Peter,
Thanks. This problem was holding up the testing of the
libffi i386 Darwin patch because Sandro has a non-EMT64
MacBook Pro. He had to resort to --disable-multi.
Jack
ps If I understand this issue correctly, even if the automake
maintainers accepted the patc
On Oct 9, 2006, at 9:27 PM, Jack Howarth wrote:
Geoff,
Can you point me to the proposed patch in the gcc-patches
mailing list archives? I can't seem to find it.
http://lists.gnu.org/archive/html/automake-patches/2006-09/msg00027.html
It's automake -patches.
Peter
Geoff,
Can you point me to the proposed patch in the gcc-patches
mailing list archives? I can't seem to find it.
Jack
On Sun, Oct 08, 2006 at 10:24:36PM -0700, Geoffrey Keating wrote:
>
> I believe trying to disable the multilib is fundamentally the wrong
> approach.
On Oct 9, 2006, at 2:24 PM, Geoffrey Keating wrote:
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 h
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
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
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
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
>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
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
10 matches
Mail list logo
