Hi, On Wed, 5 Aug 2009, George Spelvin wrote: > > Three classes of people compile git from the source: > > > > * People who want to be on the bleeding edge and compile git for > > themselves, even though they are on mainstream platforms where they > > could choose distro-packaged one; > > > > * People who produce binary packages for distribution. > > > > * People who are on minority platforms and have no other way to get git > > than compiling for themselves; > > > > We do not have to worry about the first two groups of people. It won't > > be too involved for them to install Perl on their system; after all they > > are already coping with asciidoc and xmlto ;-) > > Actually, I'd get rid of the perl entirely, but I'm not sure how > necessary the other-assembler-syntax features are needed by the > folks on MacOS X and Windows (msysgit). Don't worry for MacOSX and msysGit (or Cygwin, for that matter): all of them use GCC. > > We can continue shipping mozilla one to help the last group. > > Of course, we always need a C fallback. Would you like a faster one? Is that a trick question? :-) > > In the Makefile, we say: > > > > # Define NO_OPENSSL environment variable if you do not have OpenSSL. > > # This also implies MOZILLA_SHA1. > > > > and with your change, we would start implying STANDALONE_OPENSSL_SHA1 > > instead. But if MOZILLA_SHA1 was given explicitly, we could use that. > > Well, I'd really like to auto-detect the processor. Current gcc's > "gcc -v" output includes a "Target: " line that will do nicely. I can, > of course, fall back to C if it fails, but is there a significant user > base using a non-GCC compiler? Do you really want to determine which processor to optimize for at compile time? Build system and target system are often different... Ciao, Dscho -- 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