This is to report a successful build of GCC 4.4.2 on my laptop.

./config.guess:

i386-apple-darwin10.2.0

gcc -v:

Using built-in specs.
Target: x86_64-apple-darwin10.2.0
Configured with: ../gcc-4.4.2/configure
--prefix=/Users/*****/Documents/MyApps/Commands/GCC/MacOSX
--with-pkgversion="GNU GCC 4.4.2 Codename Lord of Compilers built Dec.
14, 2009 with GMP 4.3.1, MPFR 2.4.2, MPC 0.8.1 and Libelf 0.8.13,
bootstrapped by GCC 4.4.2 Codename Optimised Bootstrapper "
--with-libelf=/Users/****/Documents/MyApps/Commands/GCC/Dependencies//libelf-0.8.13
--enable-lto 
--with-mpc=/Users/*****/Documents/MyApps/Commands/GCC/Dependencies//mpc-0.8.1
--with-mpfr=/Users/*****/Documents/MyApps/Commands/GCC/Dependencies//mpfr-2.4.2
--with-gmp=/Users/*****/Documents/MyApps/Commands/GCC/Dependencies//gmp-4.3.1
--enable-shared --enable-static --target=x86_64-apple-darwin10.2.0
--build=x86_64-apple-darwin10.2.0 --host=x86_64-apple-darwin10.2.0
--enable-threads --enable-languages=c,c++,fortran,objc,obj-c++
--enable-werror --enable-gather-detailed-mem-stats --with-tune=core2
Thread model: posix
gcc version 4.4.2 (GNU GCC 4.4.2 Codename Lord of Compilers  built
Dec. 14, 2009 with GMP 4.3.1, MPFR 2.4.2, MPC 0.8.1 and Libelf 0.8.13,
bootstrapped by GCC 4.4.2 Codename  Optimised Bootstrapper)

Timings of build (was built with  profiledbootstrap-built GCC 4.4.2
compiled only with C, environnement variables CC="gcc -g -O3
-fno-omit-frame-pointer"):

time make profiledbootstrap
...

real    339m16.074s
user    93m54.877s
sys    13m30.623s

NB: There was a 4-hour (240 minutes) period during which the computer
was asleep and did not contribute any CPU cycles. The build time was
indeed closer to "user" than "real" - about 100 minutes or so.

Other relevant information:

uname -a:

Darwin *****-**********-MacBook.local 10.2.0 Darwin Kernel Version
10.2.0: Tue Nov  3 10:37:10 PST 2009;
root:xnu-1486.2.11~1/RELEASE_I386 i386

System Specs:

MacBook6,1 (Late 2009) Standard Configuration
Mac OS X 10.6.2
Intel Core 2 Duo 2.26 GHz
2GB DDR3 1066 MHz RAM
Xcode 3.2.1 (GCC 4.2.1 (1), Apple Inc.)

Bootstrap options:

I built a special GCC 4.4.2 from source with Xcode's default gcc 4.2.1
and all optimisation to maximum (CC="gcc -g -O3
-fno-omit-frame-pointer") and time make profiledbootstrap called
Optimised Bootstrapper . I then used the same options to build this
full version of GCC 4.4.2 and again issued time make
profiledbootstrap. The timings may not be fair because of optimisation
and the use of a highly optimised bootstrap gcc build, but the timings
are provided above. Optimised Bootstrapper took just under an hour to
build, with no native language support and only the C compiler
(because that's the only thing needed for bootstrapping GCC).

Request for update to system-specific installation instructions:

I am on Mac OS X Snow Leopard. There has been some noise around the
forums that GCC fails for various reasons. It turns out that despite
having all the requirements to run 64-bit systems, including a 64-bit
processor (an Intel Core 2 Duo), no Macs boot the 64-bit kernel by
default and only 4 (These being Mac Pros, Xserves, Macbook Pros and
iMacs) are allowed to boot it at all, leaving that the system kernel
runs 32-bit, but almost every application is 64-bit. Also, the command
uname returns i386 despite the Core 2 Duo being more of a i686 or
x86_64, a 64-bit processor. It seems therefore that config.guess
confuses itself in bitness, picking the 32-bit version called i386
rather than the correct choice, x86_64. So the recommendation is to
add an entry under Build Stats saying that 4.4.2 under
x86_64-apple-darwin10.2.0 is successful, and to add to the
system-specific installation notes to add these options to the
configure:

--host=x86_64-apple-darwin10 --target=x86_64-apple-darwin10
--host=x86_64-apple-darwin10 --with-tune=[core2 | generic | i686]

This essentially forces configure to choose the 64-bit flavour. I
selected core2 because I am not compiling executables for any other
processors - Macs have all switched to either Core 2 Duo, Core 2 Quad
or, in high-ends, to Intel Xeon, Nehalem architecture.

Reply via email to