Do we know anybody with BSDI 4.1? LC_MESSAGES may have made it into that
release, though I have no way of checking this since my support contract has
expired :-(. I'll renew, but that doesn't help for an April release.
Regards,
- Steve
----- Original Message -----
From: Tom Lane <[EMAIL PROTECTED]>
To: Bruce Momjian <[EMAIL PROTECTED]>
Cc: Steve Nunez <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, March 20, 2000 12:36 PM
Subject: Re: [BUGS] Where is a compile bug in postgresql-7.0beta2 reported?
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yes, I see it here on BSD/OS 4.01 with --enable_locale. It is from:
>
> > lc->lc_messages = setlocale(LC_MESSAGES, NULL);
>
> > BSDI does not define LC_MESSAGES as part of its setlocale() interface.
> > Is this a standard feature that BSDI is missing, or some specific
> > extension?
>
> HPUX has LC_MESSAGES, and I don't usually find them to be out on the
> bleeding edge of conformance to new standards. The HPUX man page
> for setlocale() --- which specifically lists LC_MESSAGES --- says
>
> STANDARDS COMPLIANCE
> setlocale(): AES, SVID3, XPG3, XPG4, FIPS 151-2, POSIX.1, ANSI C
>
> which are all pretty ancient. So I suspect BSDI is behind the curve.
>
> Next question is what to do about it. We could do #ifdef LC_MESSAGES,
> but what do we need to do if it's not defined?
>
> regards, tom lane
>
