From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] glibc build problem in make check
Date: Tue Feb 6 14:43:02 2001 [thread overview]
Message-ID: <20010206144218.A326@cvs.gentoo.org> (raw)
In-Reply-To: <20010206142311.C27279@cvs.gentoo.org>; from pete@gentoo.org on Tue, Feb 06, 2001 at 02:23:11PM -0700
On Tue, Feb 06, 2001 at 02:23:11PM -0700, Pete Gavin wrote:
> Hi,
>
> I tried building glibc-2.2.1 again, this time under linux-2.4.0.11-r3,
> to see if the problem was related to a reiserfs problem in the
> kernel. I got the same error that I got under linux-2.4.1-pre8. This
> happened under the make check stage of the build. Do you know anything
> about this, Achim?
>
>
> GCONV_PATH=/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/iconvdata LC_ALL=C /tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/elf/ld-linux.so.2 --library-path /tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/work/glibc-2.2.1/buildhere/math:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/elf:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/dlfcn:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/nss:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buidhere/nis:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/rt:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/resolv:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/crypt:/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/linuxthreads /tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/io/test-lfs > /tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/io/test-lfs.out
> Timed out: killed the child process
> make[2]: *** [/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/buildhere/io/test-lfs.out] Error 1
> make[2]: Leaving directory `/tmp/portage/glibc-2.2.1/work/glibc-2.2.1/io'
> make[1]: *** [io/tests] Error 2
> make[1]: Leaving directory `/tmp/portage/glibc-2.2.1/work/glibc-2.2.1'
> make: *** [check] Error 2
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.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
</quote>
So maybe we're dealing with a buggy binutils? It's happened before.
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-02-06 21:42 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 [this message]
2001-02-06 17:33 ` Pete Gavin
2001-02-06 18:52 ` drobbins
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=20010206144218.A326@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