public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: llewelly@xmission.com
To: Frank Krauss <fmfkrauss@mindspring.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error during "make bootstrap" during GCC 3.3 Creation
Date: Mon, 19 Apr 2004 21:14:00 -0000	[thread overview]
Message-ID: <s3r8ygr1xih.fsf@xmission.xmission.com> (raw)
In-Reply-To: <200404191311.30687.fmfkrauss@mindspring.com>

Frank Krauss <fmfkrauss@mindspring.com> writes:

> Thank you for looking into my Problem.
> 
> 1.  Your 100% correct about the Binutils being at the wrong Level.
>      I somehow missed seeing that in the Pre-req section and I will look into
>      updating that.


See: http://xrl.us/bwvk , and also, www.gnu.org/software/binutils .

Questions about binutils go to binutils at sources.redhat.com 

> 2.  I believe that my problem is actually caused by your 2nd suggestion
>     concerning the level of GLIBC that I'm using.
>     I didn't see any mention of a need for a specific version of
> GLIBC.

I don't either. I was sure there was one when I wrote my last post,
    but now I think I was mistaken. I *do* know some additional
    libstdc++ testcase failures occur with glibc < 2.2.5, but that
    shouldn't prevent a bootstrap. 

> 
> 3.  In other words, do I have to update my GLIBC to a specific level
>     before updating GCC?  I was under the impression that it was
>     supposed to be done the opposite way, with first GCC getting updated
>     and then using it to update GLIBC.

It depends on circumstance. I don't know all of the details.

> 
> 4.  Would you know of any doc available to show the correct procedure
>      on updating these two Components?
> 
> I have enclosed the listing of my /lib/*libc* as you requested.
> 
> Thanks again for your assistance.
> 
> Frank
> 
> output of "ls -l /lib/*libc*"
> 
> -rwxr-xr-x   1 root     root      1245005 Aug 10  1999
> /lib/libc-2.1.1.so
[snip]

2.1.1 is a very old libc. Unfortunately, upgrading libc from sources
    is difficult and error-prone. (It's not for the faint of heart,
    it's not for people who don't have full system backups, and it's
    not for people who don't have sstaticly linked copies of essential
    tools in strategic places. Nor is it for people without rescue
    disks and spare install CDs.)

Normally one upgrades libc with linux-distro-supplied packages. You'll
    have to see your distro implementor for those.

Since libc is so difficult to upgrade, I suggest you try upgrading
    binutils first, and hope that solves your problem.

  reply	other threads:[~2004-04-19 21:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 12:32 Frank Krauss
2004-04-17 13:37 ` Jack Liddle
2004-04-18 18:34   ` Frank Krauss
2004-04-18 23:33     ` Frank Krauss
2004-04-19  2:48 ` llewelly
2004-04-19 17:14   ` Frank Krauss
2004-04-19 21:14     ` llewelly [this message]
     [not found]       ` <200404192032.03563.fmfkrauss@mindspring.com>
2004-04-20 23:36         ` Frank Krauss
2004-04-21  3:17           ` llewelly
2004-04-21 16:12             ` Frank Krauss
2004-04-21 17:02               ` llewelly

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=s3r8ygr1xih.fsf@xmission.xmission.com \
    --to=llewelly@xmission.com \
    --cc=fmfkrauss@mindspring.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).