public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] glibc build problem in make check
Date: Tue Feb  6 18:52:01 2001	[thread overview]
Message-ID: <20010206185132.B540@cvs.gentoo.org> (raw)
In-Reply-To: <20010206173213.E27279@cvs.gentoo.org>; from pete@gentoo.org on Tue, Feb 06, 2001 at 05:32:13PM -0700

On Tue, Feb 06, 2001 at 05:32:13PM -0700, Pete Gavin wrote:
> On Tue, Feb 06, 2001 at 02:42:18PM -0700, drobbins@gentoo.org wrote:
> > I did a google search, and found that another person had that same problem
> > but with kernel 2.2.17.  I don't think it's a kernel issue.  It's either
> > a problem with glibc or binutils.  In a response, Andreas of SuSE says:
> > 
> > <quote>
> > Update to newer binutils,  2.10.1 should be ok.
> > 
> 
> Yeah, I've got binutils 2.10.1, and gcc-2.95.2. Maybe the bug still
> exists in the binutils 2.10.1, or there's a problem in the reiserfs
> lfs code, or something like that.

I doubt it's a ReiserFS problem -- that error is generated by the glibc
test skeleton.

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-02-07  1:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 14:24 [gentoo-dev] glibc build problem in make check Pete Gavin
2001-02-06 14:38 ` Pete Gavin
2001-02-06 21:28   ` Achim Gottinger
2001-02-06 14:43 ` drobbins
2001-02-06 17:33   ` Pete Gavin
2001-02-06 18:52     ` drobbins [this message]
2001-02-16 19:44 ` Achim Gottinger
2001-02-16 22:01   ` drobbins
2001-02-16 22:30     ` Achim Gottinger
2001-02-17 16:25       ` Achim Gottinger
2001-02-18 22:55         ` Achim Gottinger
2001-02-19  7:43           ` drobbins
2001-02-19  8:14             ` Achim Gottinger

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=20010206185132.B540@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.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