public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ible <ible_snover@bigpond.com>
To: "gcc-help" <gcc-help@gcc.gnu.org>
Cc: Dara Hazeghi <dhazeghi@yahoo.com>
Subject: Re: extremely disappointing bootstrap problems building gcc on linux :(
Date: Sun, 01 Jun 2003 12:06:00 -0000	[thread overview]
Message-ID: <20030601120600.GftH1NVj74RSb7XL0yaj4STqOtfd0xAGd5lwipSoKmo@z> (raw)
In-Reply-To: <20030521073851.73254.qmail@web41110.mail.yahoo.com>

Hi all,

I still have no luck compiling gcc 3.3 :(

I have finally upgraded my glibc to:

glibc-static-devel-2.2.5-16.2mdk
glibc_lsb-2.2.90-4mdk
glibc-devel-2.2.5-16.2mdk
glibc-2.2.5-16.2mdk

But I still get the same errors as before, with
compilation failing at g++spec.c, with different 
errors depending on which compiler i use 
(2.95.3, 2.96, 3.04)

The glibc_lsb is a leftover from the packages i 
already had installed. I left it there as I have no 
idea what it really is and it seems to be numbered 
differently to the proper glibc rpms.

I also upgraded my make to:
make-3.79.1-10mdk

but it made no difference. 

Aargh... I am now giving up, unless someone else
has had the same problem and worked out what the 
solution is.

John

  parent reply	other threads:[~2003-06-01 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030521073851.73254.qmail@web41110.mail.yahoo.com>
2003-06-01 12:06 ` ible
2003-06-01 12:06 ` ible [this message]
2003-06-01 18:36 Dara Hazeghi
     [not found] <200305171200.h4HC0acA251822@e35.co.us.ibm.com>
2003-05-19 19:37 ` Janis Johnson
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17 19:19 Dara Hazeghi
2003-05-18 12:56 ` John Sincock
2003-05-18 12:56 ` John Sincock
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=20030601120600.GftH1NVj74RSb7XL0yaj4STqOtfd0xAGd5lwipSoKmo@z \
    --to=ible_snover@bigpond.com \
    --cc=dhazeghi@yahoo.com \
    --cc=gcc-help@gcc.gnu.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).