On Fri, 9 Nov 2007, Luke Lu wrote: > > mmap(2), which git uses by default, is subject to vm limits (typically <2GB), > regardless of large file support. file `which git` will probably tell you that > it's a Mach-O executable i386 instead of x86_64. In order to get 64 bit > binaries on Mactel boxes, you'll need the -m64 flag for gcc. I suspect that > compiling with NO_MMAP option work as well. Even with NO_MMAP, git will still want to read in source files in their entirety (just with regular reads). So you'll still be VM size-limited: the mmap() will just be replaced with a malloc+read in order to avoid some broken windows mmap() behaviour. But hearing whether -m64 makes a difference would be interesting. I'm hoping OS X is LP64, not some insane half-way thing like Vista is. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
