From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=5.0 tests=DATE_IN_PAST_06_12, DKIM_ADSP_NXDOMAIN,DMARC_NONE,INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from rouge.snu.ac.kr ([147.46.102.25]) by cvs.gentoo.org with esmtp (Exim 3.22 #1) id 14VWqE-0001ND-00 for gentoo-dev@gentoo.org; Wed, 21 Feb 2001 03:49:52 -0700 Received: (from redjade@localhost) by rouge.snu.ac.kr (8.11.0/8.11.0) id f1LAogx09106 for gentoo-dev@gentoo.org; Wed, 21 Feb 2001 19:50:42 +0900 (KST) From: Kyung-hwan Kim 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 Message-ID: <20010221195042.A9090@rouge.snu.ac.kr> References: <3A90BA1F.5C3183BD@gottinger.de> <20010221024947.A7139@rouge.snu.ac.kr> <3A9350B7.41261D7A@gottinger.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A9350B7.41261D7A@gottinger.de>; from 320095285153-0001@t-online.de on Wed, Feb 21, 2001 at 06:23:03AM +0100 Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Wed Feb 21 03:50:01 2001 X-Original-Date: Wed, 21 Feb 2001 19:50:42 +0900 X-Archives-Salt: 2e6aa41c-dab9-47d2-942a-8419e68016bf X-Archives-Hash: aa578f3ce1730b673fb7fc8356660a2b > > 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