From: Eljay Love-Jensen <eljay@adobe.com>
To: "Bell, Timothy" <timothy.bell@intergraph.com>, gcc-help@gcc.gnu.org
Subject: RE: Problem Building 32-bit gcc native compiler
Date: Tue, 19 Jul 2005 22:29:00 -0000 [thread overview]
Message-ID: <6.2.1.2.2.20050719171917.02126798@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <697750C28DC0474ABF279ECB3979E3730C01CC1D@hq4.pcmail.ingr.c om>
Hi Tim,
Are you short on disk space? If not, what does...
make bootstrap
...do?
When I built (GCC 3.4.3), I used the trick of narrowly specifying my PATH...
PATH=/net/export/share/gcc-3.2/bin:/bin:/usr/bin make -j 4 CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap-lean
...which worked well for me. Avoided some undesirable interactions with Solaris's compiler. I haven't tried to build GCC 4.0 from scratch yet, though.
Oh, and my configure was...
PATH=/net/export/share/gcc-3.2/bin:/bin:/usr/bin \
/export/eljay/gcc-3.4.3/configure \
--prefix=/export/eljay/gcc34 \
--enable-languages=c,c++ \
--with-gnu-as \
--with-as=/net/export/share/gcc-3.2/bin/as \
--with-gnu-ld \
--with-ld=/net/export/share/gcc-3.2/bin/ld \
--enable-threads \
--enable-shared \
--disable-symvers \
--disable-__cxa_atexit
...which has some Solaris-isms in there. But just as an FYI, I thought I'd pass it along.
--Eljay
reference...
http://gnu.miscellaneousmirror.org/software/gcc/gcc-4.0/buildstat.html
next prev parent reply other threads:[~2005-07-19 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 19:54 Bell, Timothy
[not found] ` <697750C28DC0474ABF279ECB3979E3730C01CC1D@hq4.pcmail.ingr.c om>
2005-07-19 22:29 ` Eljay Love-Jensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-20 13:20 Bell, Timothy
[not found] ` <697750C28DC0474ABF279ECB3979E3730C01D5CE@hq4.pcmail.ingr.c om>
2005-07-20 13:35 ` Eljay Love-Jensen
2005-07-20 13:55 ` Rupert Wood
2005-07-20 12:44 Bell, Timothy
[not found] ` <697750C28DC0474ABF279ECB3979E3730C01D426@hq4.pcmail.ingr.c om>
2005-07-20 13:08 ` Eljay Love-Jensen
2005-07-20 16:45 ` Bob Proulx
2005-07-19 22:54 Bell, Timothy
2005-07-20 13:08 ` Rupert Wood
2005-07-19 19:07 Bell, Timothy
[not found] ` <697750C28DC0474ABF279ECB3979E3730C01C9DE@hq4.pcmail.ingr.c om>
2005-07-19 19:19 ` Eljay Love-Jensen
2005-07-19 17:49 Bell, Timothy
[not found] ` <697750C28DC0474ABF279ECB3979E3730BFFA46E@hq4.pcmail.ingr.c om>
2005-07-19 17:58 ` Eljay Love-Jensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.2.1.2.2.20050719171917.02126798@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=timothy.bell@intergraph.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).