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

From Andrew Dunstan
Subject Re: Compile failure on nl_langinfo
Date
Msg-id 410BC17F.4060109@dunslane.net
Whole thread Raw
In response to Re: Compile failure on nl_langinfo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:

>Euler Taveira de Oliveira <euler@ufgnet.ufg.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 configure.in 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

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Trapping QUERY_CANCELED: yes, no, maybe?
Next
From: Euler Taveira de Oliveira
Date:
Subject: Re: Compile failure on nl_langinfo