Re: Compile failure on nl_langinfo - Mailing list pgsql-hackers

From Euler Taveira de Oliveira
Subject Re: Compile failure on nl_langinfo
Date
Msg-id 20040731142346.3bcd7dd0.euler@ufgnet.ufg.br
Whole thread Raw
In response to Re: Compile failure on nl_langinfo  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Hi Peter,

> > > > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol.
> > > > How can we fix it?
> > >
> > > Put #ifdef CODESET around the offending code.
> >
> > OK. Another try.
>
> What does
>
>     nl_langinfo(NULL)
>
> return?  Probably not a valid codepage.
>
No. Just "". See
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/locale/nl_langinfo.c?rev=1.3&content-type=text/x-cvsweb-markup

Isn't it acceptable? I just got locale C at initdb. But I saw this we I try to set an specific locale:

$ initdb --locale=pt_BR
initdb: invalid locale name "pt_BR"
initdb: invalid locale name "pt_BR"
initdb: invalid locale name "pt_BR"
initdb: invalid locale name "pt_BR"
initdb: invalid locale name "pt_BR"
initdb: invalid locale name "pt_BR"
The files belonging to this database system will be owned by user "euler".
This user must also own the server process.

The database cluster will be initialized with locale C.
....

The chklocale() seems to fail. I don't set neither LC_* nor LANG.

--
Euler Taveira de Oliveira
euler (at) ufgnet.ufg.br
Desenvolvedor Web e Administrador de Sistemas
UFGNet - Universidade Federal de Goiás


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Anybody have an Oracle PL/SQL reference at hand?
Next
From: "Magnus Hagander"
Date:
Subject: plpgsql compile error on win32