On 23 Feb 2015 05:29, H.J. Lu wrote: > On Sun, Aug 19, 2012 at 2:47 AM, Ben Elliston <b...@air.net.au> wrote: > >> There are 12 existing set_cc_for_build usages in config.guess. I > >> don't think it is reasonable to require x32 not to use it without > >> providing an alternative. If you want to remove set_cc_for_build, > >> one extra usage doesn't make it much harder to do. > > > > That's what the person asking for the 12th instance said .. > > > > I don't think it's reasonable for config.guess to depend on a C > > compiler. You would not believe how many problem reports I get due to > > this. > > I realized that config.guess is more broken than I thought. Depending > on "uname -m" doesn't work with 64-bit kernel and 32-bit user space:
it's always been this way: $ uname -m x86_64 $ setarch i386 uname -m i686 $ uname -m s390x $ setarch linux32 uname -m s390 i avoid it on my own systems by doing something like: init=/usr/bin/setarch linux32 /sbin/init that way all processes spawned get the inherited value. -mike
signature.asc
Description: Digital signature
_______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
