Richard Earnshaw wrote: >> Why not fix this? For example, it could also give back configure >> options (--with-float=hard) that should be implicitly assumed to have >> been provided. > > That would be useful for GCC perhaps, but not for other projects that > use config.guess (which is part of the generic GNU infrastructure). If > those extra args could be made invisible to other users; then that might > be a way forward.
Presumably config.guess would be passed a new argument that causes it to produce this extra output. >> It really does seem like a hack to use triplets in this way; I think >> Paul's point that anything that depends on the toolchain triplet to >> determine ABI is inherently busted is pretty persuasive. > > Which means the whole GNU way of doing this has always been busted, > since that's essentially how the world has always worked... :-) Well, indeed. There's always the question of when one ought to go clean up the mess and when one ought to just go with the flow. We've seen these kinds of problems on every embedded architecture; MIPS, for example, has suffered rather badly from this problem. Deriving ABI behavior from triplets is a problem that's caused brokenness for multilib'd toolchains in various packages. -- Mark Mitchell CodeSourcery m...@codesourcery.com (650) 331-3385 x713
