On Tue, Mar 16, 2010 at 3:31 AM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: > Gary V. Vaughan schrieb: >> Unfortunately, there are still plenty of production systems with >> vendor compilers that choke unless all compound declarations can be >> determined statically at compile time, for example hpux10.20 (I can >> provide a comprehensive list of our supported platforms that exhibit >> this problem if necessary). > > Yes, a comprehensive list would be appreciated. This change is an > uglification that I personally would prefer to stay out of the code base > unless many consumers of git are hurt. > > The problem with this non-feature is that it is all too easy that new code > introduces new incompatibilities. This is probably a stupid question, but why not just build it using gcc on systems with a broken vendor compiler? You don't have to distribute gcc just to distribute binaries built with it, so it seems like there's no downside... and less suffering for the build maintainer. Have fun, Avery -- 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