public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
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	[thread overview]
Message-ID: <2455277.FQ94eXaZZo@andromeda> (raw)
In-Reply-To: <9c548fbb-46e9-4425-b5e2-44b7536c7caa@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 12498 bytes --]

  reply	other threads:[~2014-07-17  7:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  1:50 [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error Dale
2014-07-15  2:02 ` Hinnerk van Bruinehsen
2014-07-15  2:19   ` Dale
2014-07-15  2:35     ` Hinnerk van Bruinehsen
2014-07-15  3:44       ` Dale
2014-07-15  5:33 ` Dale
2014-07-15  7:04   ` Hinnerk van Bruinehsen
2014-07-15  7:40     ` Dale
2014-07-15  8:15       ` Hinnerk van Bruinehsen
2014-07-15  8:40         ` Hinnerk van Bruinehsen
2014-07-15  9:25           ` Dale
2014-07-15 18:52             ` Douglas J Hunley
2014-07-15 19:18               ` Dale
2014-07-16  7:32             ` Dale
2014-07-16  7:46               ` Helmut Jarausch
2014-07-16  8:43                 ` Dale
2014-07-16  9:19                   ` Dale
2014-07-16 10:33                     ` J. Roeleveld
2014-07-16 15:44                       ` Dark Templar
2014-07-16 17:26                         ` Dale
2014-07-16 21:09                           ` Mick
2014-07-16 21:34                             ` Dale
2014-07-17  4:52                           ` J. Roeleveld
2014-07-17  7:19                             ` J. Roeleveld [this message]
2014-07-17  9:03                               ` Dale
2014-07-17  9:19                                 ` J. Roeleveld
2014-07-17 10:45                                   ` J. Roeleveld
2014-07-18  9:18                                     ` Dale
2014-07-18  9:38                                       ` J. Roeleveld
2014-07-18 12:44                                       ` Jc García
2014-07-17  9:20                                 ` Peter Humphrey
2014-07-17 13:24                                   ` Peter Humphrey
2014-07-16 17:21                       ` Dale
2014-07-17  0:39                         ` [gentoo-user] " walt
2014-07-17  1:01                           ` Dale
2014-07-17 21:41 ` [gentoo-user] SNIP " Dale
2014-07-17 22:08   ` Mick
2014-07-18  3:55     ` Dale
2014-07-18  4:32       ` Jc García
2014-07-17 22:48   ` Peter Humphrey
2014-07-18  5:54     ` Mick
2014-07-18  8:12       ` Peter Humphrey

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=2455277.FQ94eXaZZo@andromeda \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.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