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 at least verify that
-m64 works with the existing compiler.
Jack
ps You realize of course that most fink packages outside of
the standard releases aren't available as prebuilt binaries
for download so the user has to build it locally from the
current packaging scripts.
On Sun, Oct 08, 2006 at 04:44:54PM -0700, Eric Christopher wrote:
>
> 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 to engineer something up
> in the configure, but it would only work for occasions when you already
> had a compiler installed that supported the 64-bit multilib since you'd
> need to have it around to build it. Or, as Ben said, it's only when you
> have already built the new compiler that you'll know and might as well
> pass --disable-multilib and start the build again :)
>
> -eric
