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: signature.asc
Description: Digital signature

Reply via email to