public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kyung-hwan Kim <redjade@rouge.snu.ac.kr>
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 03:50:01 2001	[thread overview]
Message-ID: <20010221195042.A9090@rouge.snu.ac.kr> (raw)
In-Reply-To: <3A9350B7.41261D7A@gottinger.de>; from 320095285153-0001@t-online.de on Wed, Feb 21, 2001 at 06:23:03AM +0100

> > 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?

I just merged it from portage directory.

> > Is there any dependence about glibc?
> 
> Everything depends on glibc. :-)

What I really want to know is how to track bugs and correct or make a
workaround complicatedly involved glibc-binutils-gcc-linux-...(etc).

> > 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.

I give you a cheer. :)

Kyunghwan



  reply	other threads:[~2001-02-21 10:49 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 [this message]
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=20010221195042.A9090@rouge.snu.ac.kr \
    --to=redjade@rouge.snu.ac.kr \
    --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