Bug#187630: libc6: localedef uses . in its input path

[barbier@linuxfr.org (Denis Barbier)]

On Sat, Apr 05, 2003 at 10:34:37AM +0900, GOTO Masanori wrote:
> At Fri, 4 Apr 2003 20:13:46 +0200,
> Denis Barbier wrote:
> > I encountered a strange error when generating locales:
> >    i18n:1: syntax error: not inside a locale definition section
> >    i18n:3: syntax error: not inside a locale definition section
> > 
> > The reason was that a file called i18n was present in current working
> > directory, and was used by localedef.  AFAICT this is not mentioned
> > in libc6 documentation.  IMO there is no reason to search for input
> > files in '.', '-i .' can be used if needed.
> > Another option would be to display the full path
> >    ./i18n:1: syntax error: not inside a locale definition section
> >    ./i18n:3: syntax error: not inside a locale definition section
> > in order to make this error message more explanatory.
> 
> Could you tell me example in detail?  I put "i18n" in the current
> working dir, but not appeared such messages.

Sure, here is a test case.
  $ echo foo > i18n
  $ localedef -i en_US -c -f UTF-8 blah
  i18n:1: syntax error: not inside a locale definition section
  Segmentation fault

Tested with libc6 2.3.2-1

Denis