From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1B87113877A for ; Thu, 17 Jul 2014 07:19:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 192A6E0974; Thu, 17 Jul 2014 07:19:53 +0000 (UTC) Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net [212.54.42.168]) by pigeon.gentoo.org (Postfix) with ESMTP id A1237E0969 for ; Thu, 17 Jul 2014 07:19:51 +0000 (UTC) Received: from [212.54.42.136] (helo=smtp5.tb.mail.iss.as9143.net) by smtpq5.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1X7fyo-0007NP-L8 for gentoo-user@lists.gentoo.org; Thu, 17 Jul 2014 09:19:50 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp5.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1X7fyo-0001o6-0O for gentoo-user@lists.gentoo.org; Thu, 17 Jul 2014 09:19:50 +0200 Received: from andromeda.localnet (unknown [213.19.196.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 54A5A4C for ; Thu, 17 Jul 2014 09:19:48 +0200 (CEST) From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error Date: Thu, 17 Jul 2014 09:19:44 +0200 Message-ID: <2455277.FQ94eXaZZo@andromeda> Organization: Antarean User-Agent: KMail/4.12.5 (Linux/3.12.21-gentoo-r1; KDE/4.12.5; x86_64; ; ) In-Reply-To: <9c548fbb-46e9-4425-b5e2-44b7536c7caa@email.android.com> References: <53C48902.2060103@gmail.com> <53C6B5CF.1060909@gmail.com> <9c548fbb-46e9-4425-b5e2-44b7536c7caa@email.android.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart1669612.27mgjIcSK6" Content-Transfer-Encoding: 7Bit X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.9 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,HTML_MESSAGE=0.001,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: cf0db4a2-9a32-4d11-9162-25eea24749d2 X-Archives-Hash: 59e61c21fbfc1f94526d86031fd052ad This is a multi-part message in MIME format. --nextPart1669612.27mgjIcSK6 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Thursday, July 17, 2014 06:52:20 AM J. Roeleveld wrote: > On 16 July 2014 19:26:39 CEST, Dale wrote: > >Dark Templar wrote: > >> When I reinstalled gcc and glibc, migrating from non-multilib amd64 > > > >arch > > > >> to multilib one, I just unpacked gentoo stage3 into temporary > > > >directory, > > > >> chrooted there, made binary packages out of installed ones (quickpkg > >> ), copied resulted binary packages and their metadata to host > >> system (i.e. moved $chroot/usr/portage/packages into > >> /usr/portage/packages) and installed those binary packages replacing > >> current ones. It's fast (you don't have to build packages from > > > >scratch), > > > >> and it didn't fail me even once, although I heard playing with glibc > >> such way may be dangerous (particularly, downgrading it). I guess it > >> works for other purposes too. > >> > >> I don't like installing from scratch if there is a way to fix it. I > >> don't like that approach 'unpack stage on top of your system', > > > >because > > > >> it will lead to system pollution: a lot of files might be no longer > >> tracked by package manager after that. > >> > >> But that's just my experience and opinion. I hope it can help you. > > > >If I can install something as a binary and then get a clean emerge -e > >system/world out of it, I think it would be OK. Thing is, I'm > >concerned > >something is amiss with the stage3 tarball. If that is the case, I > >want > >to inform the person that overseas that so it can be fixed. Installing > >Gentoo is hard enough for someone seasoned but would be a nightmare for > >someone new to Gentoo. > > > >Now to figure out what is the root problem on this thing. > > > >Dale > > > >:-) :-) > > Dale. > > I will try to use the x86 stage3 on a VM today. Will let you know how far I > get. > > -- > Joost Update: Using a 32bit VM with current x86 stage3 file, glibc builds succesfully. (On first run) Will do a second " emerge -ve @system " when this one is finished. I used the following stage file: stage3-i686-20140708.tar.bz2 I have not change anything in /etc/portage -- Joost --nextPart1669612.27mgjIcSK6 Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

On Thursday, July 17, 2014 06:52:20 AM J. Roeleveld wrote:

> On 16 July 2014 19:26:39 CEST, Dale <rdalek1967@gmail.com> wrote:

> >Dark Templar wrote:

> >> When I reinstalled gcc and glibc, migrating from non-multilib amd64

> >

> >arch

> >

> >> to multilib one, I just unpacked gentoo stage3 into temporary

> >

> >directory,

> >

> >> chrooted there, made binary packages out of installed ones (quickpkg

> >> <name>), copied resulted binary packages and their metadata to host

> >> system (i.e. moved $chroot/usr/portage/packages into

> >> /usr/portage/packages) and installed those binary packages replacing

> >> current ones. It's fast (you don't have to build packages from

> >

> >scratch),

> >

> >> and it didn't fail me even once, although I heard playing with glibc

> >> such way may be dangerous (particularly, downgrading it). I guess it

> >> works for other purposes too.

> >>

> >> I don't like installing from scratch if there is a way to fix it. I

> >> don't like that approach 'unpack stage on top of your system',

> >

> >because

> >

> >> it will lead to system pollution: a lot of files might be no longer

> >> tracked by package manager after that.

> >>

> >> But that's just my experience and opinion. I hope it can help you.

> >

> >If I can install something as a binary and then get a clean emerge -e

> >system/world out of it, I think it would be OK. Thing is, I'm

> >concerned

> >something is amiss with the stage3 tarball. If that is the case, I

> >want

> >to inform the person that overseas that so it can be fixed. Installing

> >Gentoo is hard enough for someone seasoned but would be a nightmare for

> >someone new to Gentoo.

> >

> >Now to figure out what is the root problem on this thing.

> >

> >Dale

> >

> >:-) :-)

> Dale.

> I will try to use the x86 stage3 on a VM today. Will let you know how far I

> get.

> --

> Joost

Update:

Using a 32bit VM with current x86 stage3 file, glibc builds succesfully. (On first run)

Will do a second " emerge -ve @system " when this one is finished.

I used the following stage file:

stage3-i686-20140708.tar.bz2

I have not change anything in /etc/portage

Joost

--nextPart1669612.27mgjIcSK6--