public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: mc-4.6.1 not showing graphical characters in terminal
Date: Sun, 10 Sep 2006 18:44:02 +0200	[thread overview]
Message-ID: <200609101844.06905.bo.andresen@zlin.dk> (raw)
In-Reply-To: <ee1c09$9g$1@sea.gmane.org>

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

On Sunday 10 September 2006 17:46, Peter wrote:
> > This is not connected to your profile or gcc upgrade. It's your glibc
> > upgrade. glibc-2.4.x is stricter when it comes to syntax than
> > glibc-2.3.x. Please show the output of:
>
> I did not upgrade glibc. I recompiled it with the gcc-4.1.1 upgrade.

Your emerge --info shows that you are using glibc-2.4 on an x86 stable system. 
glibc-2.4 and gcc-4.1.1 was stabilized at the exact same time (11 days ago) 
so until I see proof of the opposite I am going to assume that glibc was 
upgraded when you recompiled with gcc-4.1.1.

If you still think glibc wasn't upgraded at the same time then please emerge 
app-portage/genlop and show the output of:

# genlop sys-libs/glibc
# genlop sys-devel/gcc

> > # grep -v '^$\|^#' /etc/locale.gen
>
> en_US ISO-8859-15

So you obviously don't want utf8. Otherwise you should add a utf8 locale to 
locale.gen and follow the utf8 guide. Syntax is correct btw... As long as you 
don't want unicode.

[SNIP]

> > Also utf8 isn't the default in Gentoo (yet). /etc/env.d/03locale should
> > have been created manually when you followed [1] given that you wanted
> > utf8.
>
> I don't have an 03locale file. I manually created an 02locale file.

That was a typo. I meant 02locale. Not that it really matters though...

> > [1] http://www.gentoo.org/doc/en/utf-8.xml
>
> I have a lot to learn. As I wrote, I took a lot for granted!

AFAICT the real issue, however, seems to be the fact that sys-apps/baselayout 
has this code in the ebuild:

src_unpack() {
	[...]
	# Setup unicode defaults for silly unicode users
	if use unicode ; then
		sed -i -e '/^UNICODE=/s:no:yes:' etc/rc.conf
	fi
	[...]
}

If the unicode use flag is enabled (which it is by default in the 2006.1 
profiles) this enables unicode in /etc/rc.conf without taking the locale into 
account. That seems stupid IMO.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-10 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 20:02 [gentoo-user] mc-4.6.1 not showing graphical characters in terminal Peter
     [not found] ` <45032BAF.8020309@gmx.net>
2006-09-09 21:09   ` [gentoo-user] " Stefan Wimmer
2006-09-09 21:55 ` [gentoo-user] " Jerry McBride
2006-09-09 22:55   ` [gentoo-user] " Peter
     [not found]   ` <edvh56$vh0$1@sea.gmane.org>
2006-09-10  1:31     ` Jerry McBride
2006-09-10 11:18       ` Peter
2006-09-10 14:55         ` Bo Ørsted Andresen
2006-09-10 15:46           ` Peter
2006-09-10 16:44             ` Bo Ørsted Andresen [this message]
2006-09-10 16:34         ` Jerry McBride
2006-09-10 13:33       ` Peter
2006-09-10 15:16   ` [gentoo-user] " Lukasz Pawelczyk

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=200609101844.06905.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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