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: Wed Feb 21 06:52:01 2001 [thread overview]
Message-ID: <3A93C1F4.500B4B3C@gottinger.de> (raw)
In-Reply-To: 20010221204444.A9198@rouge.snu.ac.kr
Kyung-hwan Kim wrote:
>
> > > After merging binutils-2.10.1.0.7 and everything gose beautifully.
> > > But merging glibc-2.2.2, nothing would go its way.
> > >
> > > Do you mean that packages must be recompiled under glibc-2.2.2 and
> > > updated binutils environment?
> > No normaly that should not be neccesary.
I finished upgrading glibc to 2.2.2 on a pure rc4_pre2 system.
I used binutils-2.10.92.0.2 and I had to remove the manually created
virtual/glibc dir before I merged glibc.
I did not see any segfault yet.
achim~
> >
> > It seems that the problem is arch dependend.
> >
> > I use i686-pc-linux-gnu here. The rc4_pre2 packages use
> > i486-pc-linux-gnu
> > as default.
> >
> > I currently building glibc-2.2.2-r1 with binutils-2.10.92.0.2 on a pure
> > rc4_pre2 machine. I hope that works.
> >
> > Did the glibc test's fail on your machine when using binutils 2.10.1?
>
> Yes. :)
>
> > On a i686 target they do.
>
> Kyunghwan
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2001-02-21 13:51 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
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 [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=3A93C1F4.500B4B3C@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