Re: automatic --disable-multilib

2006-10-08 Thread Geoffrey Keating
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 w

Re: automatic --disable-multilib

2006-10-08 Thread Jack Howarth
Eric, The problem we have in fink is that the absence of a check for viable -m64 build support in the compiler causes failures on G4s and non-EMT64 hardware when the gcc4 package is built without --disable-multilib. It seems odd that out of all the checks configure does in build that it doesn't

Re: automatic --disable-multilib

2006-10-08 Thread Eric Christopher
On Oct 8, 2006, at 4:35 PM, Jack Howarth wrote: Ben, Currently on Darwin and apparently Solaris as well, we have build failures when gcc trunk is built without resorting to --disable-multilib on hardware that doesn't support 64-bits. See PR21561. It'd be possible for non-cross compiles t

Re: automatic --disable-multilib

2006-10-08 Thread Jack Howarth
Ben, Currently on Darwin and apparently Solaris as well, we have build failures when gcc trunk is built without resorting to --disable-multilib on hardware that doesn't support 64-bits. See PR21561. Jack ps I am told for example that the builds of gcc trunk fail on the non-EM

Re: automatic --disable-multilib

2006-10-08 Thread Ben Elliston
>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? The capability of the build system compiler is meaningless for multilibs. Whether or not multilibbing will work depends on whet

automatic --disable-multilib

2006-10-08 Thread Jack Howarth
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. I

Re: [RFC PATCH]: enable building GMP/MPFR in local tree

2006-10-08 Thread Steve Kargl
On Sun, Oct 08, 2006 at 04:42:29PM -0400, Kaveh R. GHAZI wrote: > > 3. Assuming we're merciless in requiring an up-to-date version of > GMP/MPFR in #2, remove hacks in fortran that work around bugs in older > copies of GMP/MPFR. We can also do this separately after everything > settles down. Ca

[RFC PATCH]: enable building GMP/MPFR in local tree

2006-10-08 Thread Kaveh R. GHAZI
It turned out to be much easier than I thought to decipher the top level machinery and get GMP/MPFR building inside the GCC tree. :-) The patch below is sufficient to build both GMP and MPFR and use them when linking cc1. When I add in my previous patch for PR 29335 to evaluate sin/cos/tan at co