Jack Howarth <[EMAIL PROTECTED]> writes: > Shouldn't configure in gcc be made to > automatically test if -m64 is working on > the build machine in question and automatically > invoke --disable-multilib if not? Currently > on Darwin for example we have to explicitly > invoke --disable-multilib when building on > G4's or non-EMT64 Macintel machines. It would > much better if configure would automatically > handle this.
I believe trying to disable the multilib is fundamentally the wrong approach. I have posted a patch which I believe is the correct approach to the automake list, where it is awaiting review.