On Thu, 17 Jan 2008, H.Merijn Brand wrote: > I think not building with a non-gcc C compiler could be a showstopper for us - > our policy is to compile all packages (yes, even gcc itself) using HP's > ANSI C and C++ compilers unless it's literally impossible to do so (the > only package exception so far is "pdftk" and that's only because HP don't > have a compiler equivalent to gcj). Is HP's ANSI C compiler C99 or C89? Git is sort of officially C89, but most developers use C99 compilers, so there's a bunch of C99-isms; seems to me like a slew of "inline" as a keyword and three C++/C99 comments. If the compiler is supposed to be C99, the issues should be reported to HP and the gcc people, since "make CFLAGS=-std=c99" has no problem with git, suggesting that there's some issue with interpretation of the standard for one or the other. -Daniel *This .sig left intentionally blank* - 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
