Hello everyone, I just wanted to know how much time it takes to GCC43 to compile. I've been doing this for more than an hour, and it seems that it's never going to end. I'm on a MacBook Pro, Santa Rosa generation. Thank you all, aa
GCC can take a _long_ time to compile. On Thu, Mar 20, 2008 at 8:45 PM, Alejandro Aragón <alejandro.aragon@gmail.com> wrote:
Hello everyone,
I just wanted to know how much time it takes to GCC43 to compile. I've been doing this for more than an hour, and it seems that it's never going to end. I'm on a MacBook Pro, Santa Rosa generation. Thank you all,
aa
-- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59
On Thu, Mar 20, 2008 at 5:47 PM, James Sumners <james.sumners@gmail.com> wrote:
GCC can take a _long_ time to compile.
Um, yeah. The first I ever tried to build a new gcc, it took me several *days*. But that was a long time ago and a hardware platform far far away (you kids ever use a SPARCstation 20?). Yes, it will take a long time. An hour is nothing to a gcc compile job. It will finish in hours, not days, but it's a big job. -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
paul> (you kids ever use a SPARCstation 20?). No, but I've used a Sun/100 and Sun-2/120. ;-) Back when I was (practically) a kid ... -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/
paul beard wrote:
On Thu, Mar 20, 2008 at 5:47 PM, James Sumners <james.sumners@gmail.com> wrote:
GCC can take a _long_ time to compile.
Um, yeah. The first I ever tried to build a new gcc, it took me several *days*. But that was a long time ago and a hardware platform far far away (you kids ever use a SPARCstation 20?).
Yes, but I think that came around *after* the PDP 11s, the Varian 620i and the EAI 8400 (full flight simulation of 747 w/Space Shuttle piggyback in 48K of *core*)! [Not to mention the Burroughs B-5500 from college. And I don't even remember the numbers of the patch-cord computers.] In A Chord, Tom Condon Bass, Agate Passage Quartet Bass & Proud Member, Kitsap Chordsmen Dir. Music Education, Evergreen District, BHS
On Mar 20, 2008, at 19:45, Alejandro Aragón wrote:
I just wanted to know how much time it takes to GCC43 to compile. I've been doing this for more than an hour, and it seems that it's never going to end. I'm on a MacBook Pro, Santa Rosa generation. Thank you all,
On a PowerBook G4 1.5 GHz, it took around six hours to compile gcc 4.something. On a MacBook Pro 2.2 GHz (Santa Rosa), it took between one and two hours.
1 hour, 40 minutes. GCC is huge! Now that I compiled a newer release of GCC, I can configure a package using ./configure CXX=/opt/local/bin/g++ Now, what it's bothering me, is that when you include a file in the code like #include <iostream> it will refer to the old gcc library, not to the new one right? Even if I specify the location of the header files with -I/opt/loca/include/gcc, why is the compilation choose my specified files instead of the usual /usr/include files? Please help, aa On Fri, 2008-03-21 at 00:50 -0500, Ryan Schmidt wrote:
On Mar 20, 2008, at 19:45, Alejandro Aragón wrote:
I just wanted to know how much time it takes to GCC43 to compile. I've been doing this for more than an hour, and it seems that it's never going to end. I'm on a MacBook Pro, Santa Rosa generation. Thank you all,
On a PowerBook G4 1.5 GHz, it took around six hours to compile gcc 4.something. On a MacBook Pro 2.2 GHz (Santa Rosa), it took between one and two hours.
participants (6)
-
Alejandro Aragón
-
James Sumners
-
paul beard
-
Ryan Schmidt
-
skip＠pobox.com
-
Thomas Condon