On Wed, 2009-04-22 at 15:04 -0400, Tom Lane wrote: > Callum Lerwick <seg haxxed com> writes: > > On Wed, 2009-04-22 at 13:59 -0400, Tom Lane wrote: > >> That doesn't solve the problem. The part of the problem that's actually > >> not solved today is the /usr/bin/foo-config problem. Without a fix for > >> that, making it a bit easier to deal with include-file diffs isn't > >> worth anything. > > > The same way cross compilation identifies gcc and strip and whatnot. > > Prefix it with the architecture. > > Which immediately breaks all the upstream configure scripts that are > trying to use the config program in the first place. Native compilation will work just fine. The un-prefixed config-foo remains in place for the native architecture. Just like gcc. And yes, it will break build scripts. Because the build scripts are depending on something that is _broken_right_now_. That's the whole point here.
Description: This is a digitally signed message part