From: Dara Hazeghi <dhazeghi@yahoo.com>
To: jss@au.mensa.org
Cc: gcc-help@gcc.gnu.org
Subject: Re: extremely disappointing bootstrap problems building gcc on linux :(
Date: Sat, 17 May 2003 19:19:00 -0000 [thread overview]
Message-ID: <7005290C-889C-11D7-9A91-000393681B36@yahoo.com> (raw)
A couple of points.
1. gcc 3.2.X and previous could not be built within their source
directory: ie "cd gcc-3.2.3 && ./configure && make" generally failed.
This may account for the -lgcc_eh problem. This was unfortunately not
well documented.
2. diff files do not apply to tarballs. Period. Diffs apply only to
regular directories. ie tar -xzf gcc-3.2.2.tar.gz && patch -p0 -E <
gcc-3.2.2-3.2.3.diff should work fine.
3. --enable-shared and --enable-threads are I believe the default on
Linux. It appears that you may have found a bug in configure on gcc
3.3. Please just do a vanilla configure without any options, and see if
this still fails.
3.5. What version of GNU make are you using? There have been a few
which have worked rather less than well (I recall 3.78 had significant
issues).
4. Quite a number of people have successfully built gcc 3.3 on Linux
(and elsewhere). If you look at
http://gcc.gnu.org/gcc-3.3/buildstat.html , you'll see at least 10
people have successfully built gcc 3.3. So while I sympathize with your
frustration, please remember that we do not have access to your exact
setup, we are a volunteer project, and it is very difficult to test
every possible environment.
Thanks,
Dara
next reply other threads:[~2003-05-17 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 19:19 Dara Hazeghi [this message]
2003-05-18 12:56 ` John Sincock
2003-05-18 12:56 ` John Sincock
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 18:36 Dara Hazeghi
[not found] <20030521073851.73254.qmail@web41110.mail.yahoo.com>
2003-06-01 12:06 ` ible
2003-06-01 12:06 ` ible
[not found] <200305171200.h4HC0acA251822@e35.co.us.ibm.com>
2003-05-19 19:37 ` Janis Johnson
2003-05-17 12:00 John Sincock
2003-05-17 12:00 John Sincock
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=7005290C-889C-11D7-9A91-000393681B36@yahoo.com \
--to=dhazeghi@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jss@au.mensa.org \
/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).