Bugzilla Bug 125264

./configure and ./etc/configure report:

configure: error: werror: invalid feature name

I'm using et_EE locales.

These can be easily fixed by sys-devel/flex/files/flex-configure-LANG.patch,
but there are a lot of scripts in ./gdb/ which also result in various issues.
Replacing a-z with [:lower:], A-Z with [:upper:], a-zA-Z with [:alpha:], 0-9
with [:digit:] and a-zA-Z0-9 with [:alnum:] in some statements might be the
solution, but it might turn out to be quite risky.

As a (temporary) solution i would recommend just placing LC_ALL=C somewhere
along the process.

*** Bug 126062 has been marked as a duplicate of this bug. ***

(In reply to comment #0)
> ./configure and ./etc/configure report:
> 
> configure: error: werror: invalid feature name
> 
> I'm using et_EE locales.
(that will be a kind of personal letter)

Tere!

i use also et_EE.utf8

as i have used gentoo for few days now, could you suggest me some reading about
gentoo locales & some additional information about why it happens?

i havent yet used this portage enough to be able to view source and make up a
clear picture about this thing myself -- have been windows user mostly. just
thinking about where to begin if i want to understand, how linux is made ;)

also, is where is good place for this LC_ALL=C, if i dont want to change my
locale?

PS. if you dont mind, is this too somehow related to et_EE that samba does not
show 

(In reply to comment #0)
> ./configure and ./etc/configure report:
> 
> configure: error: werror: invalid feature name
> 
> I'm using et_EE locales.
(that will be a kind of personal letter)

Tere!

i use also et_EE.utf8

as i have used gentoo for few days now, could you suggest me some reading about
gentoo locales & some additional information about why it happens?

i havent yet used this portage enough to be able to view source and make up a
clear picture about this thing myself -- have been windows user mostly. just
thinking about where to begin if i want to understand, how linux is made ;)

also, is where is good place for this LC_ALL=C, if i dont want to change my
locale?

PS. if you dont mind, is this too somehow related to et_EE that samba does not
show õäöü correctly, when going to WinXP machine? When accessing gentoo
from XP, it's OK. By docs, there should be no problem when utf8 is selected for
both samba and my filesystem?

> These can be easily fixed by sys-devel/flex/files/flex-configure-LANG.patch,
> but there are a lot of scripts in ./gdb/ which also result in various issues.
> Replacing a-z with [:lower:], A-Z with [:upper:], a-zA-Z with [:alpha:], 0-9
> with [:digit:] and a-zA-Z0-9 with [:alnum:] in some statements might be the
> solution, but it might turn out to be quite risky.
> 
> As a (temporary) solution i would recommend just placing LC_ALL=C somewhere
> along the process.
> 

(In reply to comment #2)
> as i have used gentoo for few days now, could you suggest me some reading about
> gentoo locales & some additional information about why it happens?
The only reading material i could think of is the gentoo localization guide at
http://www.gentoo.org/doc/en/guide-localization.xml

As i'm also quite new to linux, i don't have deep knowledge of locales. This
specific bug, however is caused by shell scripts, that use character ranges
like a-zA-Z for sed and similar statements to match all letters of the
alphabet. Unfortunately this only works with some alphabets. The Estonian
alphabet, as you already may know, does not end with a Z:

abcdefghijklmnopqrs

(In reply to comment #2)
> as i have used gentoo for few days now, could you suggest me some reading about
> gentoo locales & some additional information about why it happens?
The only reading material i could think of is the gentoo localization guide at
http://www.gentoo.org/doc/en/guide-localization.xml

As i'm also quite new to linux, i don't have deep knowledge of locales. This
specific bug, however is caused by shell scripts, that use character ranges
like a-zA-Z for sed and similar statements to match all letters of the
alphabet. Unfortunately this only works with some alphabets. The Estonian
alphabet, as you already may know, does not end with a Z:

abcdefghijklmnopqrsšzžtuvwõäöüxy

Therefore, when the system locales are set to et_EE, the Estonian alphabet is
used by sed and on many other utilities, and a-z only matches
abcdefghijklmnopqrsšz and leaves out žtuvwõäöüxy. So some parts of the
programs depending on a-z matching all letters will inevitably fail or produce
wrong results.

> i havent yet used this portage enough to be able to view source and make up a
> clear picture about this thing myself -- have been windows user mostly. just
> thinking about where to begin if i want to understand, how linux is made ;)
Gentoo certainly seems the right place to start for people interested in
undestanding linux.

> also, is where is good place for this LC_ALL=C, if i dont want to change my
> locale?
Can't think of any. Well, you could set another locale for just the root user.
Maybe this would help, but i'm not sure. What i suggested as a solution to this
specific bug was setting LC_ALL in the ebuild itself, so when emerging gdb,
LC_ALL=C would be set during the emerge in that environment.

> PS. if you dont mind, is this too somehow related to et_EE that samba does not
> show õäöü correctly, when going to WinXP machine? When accessing gentoo from
> XP, it's OK. By docs, there should be no problem when utf8 is selected for both
> samba and my filesystem?
My guess would be, that windows does not use utf8.

Feel free to mail me personally (in Estonian, if you like) on issues not
relating to the bug at hand. This is a bug-tracking portal, not a forum. People
may get angry. :)

(In reply to comment #0)
> ./configure and ./etc/configure report:
> 
> configure: error: werror: invalid feature name
> 
> I'm using et_EE locales.
> 
> These can be easily fixed by sys-devel/flex/files/flex-configure-LANG.patch,
> but there are a lot of scripts in ./gdb/ which also result in various issues.
> Replacing a-z with [:lower:], A-Z with [:upper:], a-zA-Z with [:alpha:], 0-9
> with [:digit:] and a-zA-Z0-9 with [:alnum:] in some statements might be the
> solution, but it might turn out to be quite risky.
> 
> As a (temporary) solution i would recommend just placing LC_ALL=C somewhere
> along the process.
> 

Is there any open discussion about doing this thing globally? As this is a
common error, i have to choose -- do i switch to english locale or do i start
some search-and-replace series by myself as this is way too common error.

Which discussion list addresses such kind of problems? Is there any utf
discussion list -- as i see, there are many utf8 problems around and they
should be addressed separately, working out common solutions, as repairing them
one-by-one would take a lot of time.

> Which discussion list addresses such kind of problems? Is there any utf
> discussion list -- as i see, there are many utf8 problems around and they
> should be addressed separately, working out common solutions, as repairing them
> one-by-one would take a lot of time.

I mean -- there is a Bug with a capital: gentoo lacks utf-8 bug. I have tried
about 6 emerges today and about 4 have been failed, most probably because of my
locale. Sending those bug reports here one-by-one would be the least effective
solution.

There should be discussion group, which contains people, who have currently
repaired those errors and know, how to do it, which are possible side-effects
and so on (i'm talking about installation-script related ones - others like
XMMS showing many utf8 filenames as mess and so on, are as addition, but would
have one specific group also, as there are specific group of "utf8 users").

There should be scripts, which can find all installation scripts and makefiles,
which do possibly have such a bug -- like searching [A-Z] everywhere and
reporting all places, where it occurs. This discussion list should seek such
patterns in a similar way as virus-researchers search for virus patterns, and
work out common solutions to all of them.

thi issue has nothing to do with unicode

(In reply to comment #6)
> thi issue has nothing to do with unicode
> 

Ok, i say it more generally -- localization. I mean, supporting characters from
different languages effectively.

Just confirming that bug also exists with gdb-6.4-r4

fixed in cvs

(In reply to comment #9)
> fixed in cvs

It still doesn't seem to work:

make[4]: Leaving directory `/var/tmp/portage/gdb-6.4-r4/work/gdb-6.4/opcodes'
make[3]: Leaving directory `/var/tmp/portage/gdb-6.4-r4/work/gdb-6.4/opcodes'
make[2]: Leaving directory `/var/tmp/portage/gdb-6.4-r4/work/gdb-6.4/opcodes'
Configuring in ./etc
make[1]: Leaving directory `/var/tmp/portage/gdb-6.4-r4/work/gdb-6.4'
configure: error: werror: invalid feature name
make[1]: *** [configure-etc] Error 1
make: *** [all] Error 2

ok, ive spent some time hacking on gdb-6.5 ... that version should be good to
go :)

(In reply to comment #11)
> ok, ive spent some time hacking on gdb-6.5 ... that version should be good to
> go :)

Not quite. Add LC_ALL=C into gdb/Makefile.in, otherwise locale-sensitive sed
statements in observer.sh, Makefile.in etc will still break it!

I had to revert the patch because it seems to make gdb crash for both me and
lu_zero (amd64 and ppc32).

> Not quite. Add LC_ALL=C into gdb/Makefile.in, otherwise locale-sensitive sed
> statements in observer.sh, Makefile.in etc will still break it!

huh ?  read the gdb-6.5-locale.patch, i did both of these things

> I had to revert the patch because it seems to make gdb crash for both me and
> lu_zero (amd64 and ppc32).

you cant really expect me to figure out "seems to make gdb crash" do you ?  try
giving more information as to the problem you're seeing

Sorry, I gave the information to solar, and then forgot to report here.

Basically, gdb will end up "Abort" as soon as you tried to use it. Luca was
able to reproduce with "gdb --args mplayer". I don't have the core file at hand
but if you build gdb on any chroot on any amd64 devbox, and try to run anything
through it, you'll find it :)

fixed in cvs, Makefile.in patch was slightly wrong