From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error
Date: Tue, 15 Jul 2014 04:35:59 +0200 [thread overview]
Message-ID: <20140715023559.GB28589@TranscendTheRubicon.alshain.ring0> (raw)
In-Reply-To: <53C48FAF.9030507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
On Mon, Jul 14, 2014 at 09:19:27PM -0500, Dale wrote:
> Hinnerk van Bruinehsen wrote:
> >
>
> >
>
> > Hi Dale,
>
> >
>
> > first you should check if you have this line in your
> /etc/locale.gen:
>
> > en_US.UTF-8 UTF-8
>
> >
>
> > If you do, run locale-gen to create the locale. This should
> in theory fix the
>
> > LC_<foo> errors (Note: there are some LC_ settings best
> left undisturbed,
>
> > especially setting LC_ALL to something other than "C" tends
> to break stuff).
>
> 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.
>
> >
>
> >
>
> > The other error you get (glibc failing to install) seem to be
> caused by an old
>
> > kernel version that wouldn't be compatible with the newer
> glibc. So I'd
>
> > recommend that you try to update your kernel first.
>
> >
>
> > WKR
>
> > Hinnerk
>
> 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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-07-15 2:36 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 [this message]
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
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=20140715023559.GB28589@TranscendTheRubicon.alshain.ring0 \
--to=h.v.bruinehsen@fu-berlin.de \
--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