public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Sincock <jss@au.mensa.org>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc-help@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: extremely disappointing bootstrap problems building gcc on linux :( (probably solved)
Date: Tue, 20 May 2003 12:40:00 -0000	[thread overview]
Message-ID: <20030520124000.i12GtWyQCNu2I81B3-uyniZCZXOvJh_cBo8J3jV-pE4@z> (raw)
In-Reply-To: <20030519123533.A3323@us.ibm.com>

Hi Janis

Actually I wasnt building in the source directory. I was building in a
separate directory as recommended.

On Tuesday 20 May 2003 05:05 am, you wrote:
> It looks as if you are building in the source directory; is that
> correct?  The installation producedures strongly recommend that GCC be
> built in a separate directory, e.g.

Yesterday I managed to build just the 3.3 C compiler (using
--enable-languages=c), without any problems at all, using gcc 2.95.3 ... 
So, it looks like it was just my glibc, ruining the bootstrap of g++:

The thing that threw me was the successful build report for 3.2.2, 
from someone with mandrake 8.2, glibc-2.2.4-26.2mdk

So it looked to me as if my glibc-2.2.4-25mdk would probably 
be ok... 

I wouldnt have thought it likely there would be any important changes 
between my glibc-2.2.4-25mdk and the successful glibc-2.2.4-26.2mdk 
... obviously there is though.

I expect I will have no problems building the full gcc 3.3 with all
languages enabled, when i have upgraded my glibc and tried again.

I will probably do that this weekend and send in a quick report to this
list if it is succesful...

Thanks again to all who made any suggestions etc

John

  reply	other threads:[~2003-05-20 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305171200.h4HC0acA251822@e35.co.us.ibm.com>
2003-05-19 19:37 ` extremely disappointing bootstrap problems building gcc on linux :( Janis Johnson
2003-05-20 12:40   ` John Sincock [this message]
2003-05-20 12:40   ` extremely disappointing bootstrap problems building gcc on linux :( (probably solved) John Sincock
     [not found]   ` <200305201240.h4KCeR82101192@e6.ny.us.ibm.com>
2003-05-20 16:27     ` Janis Johnson

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=20030520124000.i12GtWyQCNu2I81B3-uyniZCZXOvJh_cBo8J3jV-pE4@z \
    --to=jss@au.mensa.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=janis187@us.ibm.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).