Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Ian Chilton <mailinglist@ichilton.co.uk>
Cc: linux-mips@oss.sgi.com
Subject: Re: Problem with the new glibc-2.0.6
Date: Thu, 28 Sep 2000 01:03:41 +0200	[thread overview]
Message-ID: <20000928010341.A1834@bacchus.dhis.org> (raw)
In-Reply-To: <20000927214754.A20741@woody.ichilton.co.uk>; from mailinglist@ichilton.co.uk on Wed, Sep 27, 2000 at 09:47:54PM +0100

On Wed, Sep 27, 2000 at 09:47:54PM +0100, Ian Chilton wrote:

> I built the older glibc 2.0.6 fine, but had problems with egcs when I built dynamically, and ldconfig would not work...so, I started again...
> 
> However, the new glibc that was released the other day, does not work :(
> 
> I am using binutils 2.8.1 and egcs 1.0.3a
> 
> Any ideas?

The common dominator of the bug reports I have is building with binutils
2.8.1, so I'll have to take another look at this piece of sh^H^Hpleasure.

  Ralf

      reply	other threads:[~2000-09-27 23:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-27 20:47 Problem with the new glibc-2.0.6 Ian Chilton
2000-09-27 23:03 ` Ralf Baechle [this message]

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=20000928010341.A1834@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mailinglist@ichilton.co.uk \
    /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