From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error
Date: Mon, 14 Jul 2014 22:44:32 -0500 [thread overview]
Message-ID: <53C4A3A0.9060104@gmail.com> (raw)
In-Reply-To: <20140715023559.GB28589@TranscendTheRubicon.alshain.ring0>
Hinnerk van Bruinehsen wrote:
> On Mon, Jul 14, 2014 at 09:19:27PM -0500, Dale wrote:
>>
>> Howdy,
>>
>> I looked at that file. On both my systems, it is not a text file. When I
>> look at it in a file manager, Konqueror via fish, it shows up as "GENESIS
>> rom" for type. Since it is not text on either of my machines, I'm nervous
>> about editing that thing. Are we certain it is safe to mess with??? O_O
> Here's the contents of mine:
>
> ==============BEGIN====================
> # /etc/locale.gen: list all of the locales you want to have on your system
> #
> # The format of each line:
> # <locale> <charmap>
> #
> # Where <locale> is a locale located in /usr/share/i18n/locales/ and
> # where <charmap> is a charmap located in /usr/share/i18n/charmaps/.
> #
> # All blank lines and lines starting with # are ignored.
> #
> # For the default list of supported combinations, see the file:
> # /usr/share/i18n/SUPPORTED
> #
> # Whenever glibc is emerged, the locales listed here will be automatically
> # rebuilt for you. After updating this file, you can simply run `locale-gen`
> # yourself instead of re-emerging glibc.
>
> #en_US ISO-8859-1
> en_GB.UTF-8 UTF-8
> en_US.UTF-8 UTF-8
> de_DE.UTF-8 UTF-8
> #ja_JP.EUC-JP EUC-JP
> #ja_JP.UTF-8 UTF-8
> #ja_JP EUC-JP
> #en_HK ISO-8859-1
> #en_PH ISO-8859-1
> #de_DE ISO-8859-1
> #de_DE@euro ISO-8859-15
> #es_MX ISO-8859-1
> #fa_IR UTF-8
> #fr_FR ISO-8859-1
> #fr_FR@euro ISO-8859-15
> #it_IT ISO-8859-1
>
> =================END=================
> Note that I also enable 2 other (en_GB and de_DE) that you probably don't
> need.
>
I thought that should be a text file. I know I had to edit mine on the
new rig a long time ago but was to chicken to try it. I opened a weird
file once and made a mess so I didn't want to try that again. I wonder,
that likely came from the stage3 tarball that way. Bug maybe?? Some
files I just copied over but some I can't since one is 64 bit and one 32
bit. Example, parts of make.conf was a serious no on that.
I'll test this on the old rig first. ;-) May even just rename it and
start fresh, just in case.
>> This is interesting. I'm using this version: 3.15.5-gentoo According to
>> equery, that's as new as it gets. I thought about going back to a older
>> version but that seemed odd given the error. I been dealing with this for
>> about two days now. My 3 lb mini sledge is starting to look interesting.
>> @_@
>>
>> Thoughts?
> That's interesting: maybe that kernel is too new. Which version of glibc is
> installed right now (It may be helpful to make a guess which kernel version
> should work). Otherwise according to the Changelogs of gentoo-sources and glic
> the kernel version was something around 3.6.x when glibc-2.17 was added to the
> tree.
>
> WKR
> Hinnerk
That's why I decided to just ask. The version is 2.17. We have storms
close by so I shutdown the rig but pretty sure it was just a recompile
of the same version. Once this storm passes, I'll try a newer version.
Thanks. Maybe this will get things moving again.
Dale
:-) :-)
next prev parent reply other threads:[~2014-07-15 3:44 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 [this message]
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
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=53C4A3A0.9060104@gmail.com \
--to=rdalek1967@gmail.com \
--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