Skip site navigation (1) Skip section navigation (2)

Re: Compile failure on nl_langinfo

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Euler Taveira de Oliveira <euler(at)ufgnet(dot)ufg(dot)br>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Compile failure on nl_langinfo
Date: 2004-07-31 15:57:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Tom Lane wrote:

>Euler Taveira de Oliveira <euler(at)ufgnet(dot)ufg(dot)br> writes:
>>I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol.
>>How can we fix it?
>>1) just define it on when we don't have it. Like this:
>You've got to be kidding.  That will cause get_encoding_from_locale to
>return some random bit of information (whatever is mapped to zero),
>with who-knows-what result.
>A configure-time probe seems unnecessary anyway, since we can just do
>"#ifdef CODESET" in initdb.c.  The real question is what we should do
>if it isn't defined.  We can certainly make get_encoding_from_locale
>return NULL, but it looks like initdb will behave moderately
>unpleasantly if we do that (ie, force you to specify -E in most cases).
>Is there any reasonable fallback behavior?

A quick Google shows Mozilla falling back to ISO-8859-1



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-07-31 16:25:58
Subject: Anybody have an Oracle PL/SQL reference at hand?
Previous:From: Tom LaneDate: 2004-07-31 15:54:59
Subject: Trapping QUERY_CANCELED: yes, no, maybe?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group