This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/53883] GCC 4.7.1 doesn't build on Mac OS X 10.4.11 Tiger/PowerPC (32-bit), at least with MacPorts
- From: "dwalker07 at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 14 Jul 2012 18:52:42 +0000
- Subject: [Bug driver/53883] GCC 4.7.1 doesn't build on Mac OS X 10.4.11 Tiger/PowerPC (32-bit), at least with MacPorts
- Auto-submitted: auto-generated
- References: <bug-53883-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53883
--- Comment #7 from Daryle Walker <dwalker07 at yahoo dot com> 2012-07-14 18:52:42 UTC ---
(In reply to comment #6)
> *-darwin8 assumes ppc64 multilib, try --disable-multilib.
I added that for my second try:
//===
cd ..
gnutar -cjf gcc-obj.tar.bz2 gcc-obj
rm -r gcc-obj
mkdir gcc-obj
cd gcc-obj
../gcc/configure --with-gmp=/opt/local --with-mpfr=/opt/local
--with-mpc=/opt/local --disable-multilib
make | tee ~/making1.txt
make | tee -a ~/making1.txt
make -k check | tee -a ~/making1.txt
//===
I ran the main "make" twice because I thought it ended by timing out. But I
think it just succeeded, since the second one was a bunch of no-ops.
The third "make," for testing, is still going on. So far, I've been getting
all FAIL. (I don't have the "autogen" program.) The main compile took over a
day; how long will the testing take? Should I just quit it and "make install"?
Or install "autogen" and test again instead?