http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #8 from Jack Howarth 2011-07-30
14:22:07 UTC ---
Also, while I don't have a Core Solo or Core Duo machine to test this on, I
would expect this issue to exist on other i386-*-* targets. The default build
will create a multilibs for x8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #7 from Jack Howarth 2011-07-30
14:06:08 UTC ---
How would I perform a cross-compilation in this situation? I considered that
option but isn't cross-compilation designed for the situation when neither the
code generated by the base co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #5 from Andreas Schwab 2011-07-30 07:51:29
UTC ---
If you want to build x86-64 multilib natively you must use a capable host.
Otherwise force cross compilation.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #4 from Jack Howarth 2011-07-30
02:58:20 UTC ---
(In reply to comment #1)
> Use --disable-multilib.
Not an option for us on fink since the same packaging script has to both list
the built shared libraries
and run on both non-EMT64 an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #3 from Jack Howarth 2011-07-29
23:43:12 UTC ---
This section of configure appears unprepared for the possibility of compiling
on i386-apple-darwin* with a multilib that can't be executed on the non-EMT64
cpu...
# Check that the com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #2 from Jack Howarth 2011-07-29
23:35:46 UTC ---
Created attachment 24867
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24867
config.log file from x86_64 multilib directory on Core Duo (non-EMT64)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49909
--- Comment #1 from Andrew Pinski 2011-07-29
23:35:13 UTC ---
Use --disable-multilib.
