From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] glibc-2.2.2 / binutils-2.1.10.0.7 are incompatible/buggy!!!!! Don't use them on rc4_pre
Date: Tue Feb 20 22:49:01 2001 [thread overview]
Message-ID: <3A9350B7.41261D7A@gottinger.de> (raw)
In-Reply-To: 20010221024947.A7139@rouge.snu.ac.kr
Kyung-hwan Kim wrote:
> On Mon, Feb 19, 2001 at 07:15:59AM +0100, Achim Gottinger wrote:
> > Hi folks,
> >
> > During compilation here I found that latest binutils segfault's during
> > linking of mpeg2_movie so it seems to be abit buggy.
> >
> > With Glibc-2.2.2 some packages like daemontools/pam needs to be patched
> > to compile since there where some so
> > called header cleanups done in this release.
> >
> > Please use glibc-2.2.1 and binutils-2.1.10 until I have updated all
> > packages that needs patching.
>
> I merged glibc-2.2.2 two days ago.
> Files including ls, make, tar... got segmentation fault and failed.
>
Did you compile it or did you use the package from gentoo-updates?
>
> Is there any dependence about glibc?
Everything depends on glibc. :-)
>
> Or safe way to test new glibc/binutils and packages which is dependent
> on them?
I will upload a build environment this week. This can be used for such
tests.
>
>
achim~
>
> Kyunghwan Kim
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-02-21 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 23:42 [gentoo-dev] glibc-2.2.2 / binutils-2.1.10.0.7 are incompatible/buggy!!!!! Don't use them on rc4_pre Achim Gottinger
2001-02-20 10:50 ` Kyung-hwan Kim
2001-02-20 22:49 ` Achim Gottinger [this message]
2001-02-21 3:50 ` Kyung-hwan Kim
2001-02-21 1:38 ` Achim Gottinger
2001-02-21 3:14 ` Achim Gottinger
2001-02-21 3:56 ` Kyung-hwan Kim
2001-02-21 4:20 ` Achim Gottinger
2001-02-21 4:44 ` Kyung-hwan Kim
2001-02-21 6:52 ` 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=3A9350B7.41261D7A@gottinger.de \
--to=320095285153-0001@t-online.de \
--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