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