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

Re: Fw: Case Insensitive Test

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Chad R(dot) Larson" <chad(at)eldocomp(dot)com>,Larry Rosenman <ler(at)lerctr(dot)org>, Donald Fraser <demolish(at)cwgsy(dot)net>,"[ADMIN]" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Fw: Case Insensitive Test
Date: 2003-09-26 14:54:47
Message-ID: 20030926074907.C4723@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Fri, 26 Sep 2003, Tom Lane wrote:

> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> >> I've been through them.  None of 'em turn off // comments.  Or #-sign
>
> > On at least some versions of gcc it looks like --std=c89 turns them off
>
> Hmm, I haven't tried that in particular.  I wonder what else it does?

It looks from the headers, that by default that'll not define a bunch of
extensions stuff.  It's apparently enough stuff that even if I get around
the immediate problem I had I get a complaint about SIG_SETMASK being
undeclared (it looks like it's only defined when __USE_POSIX).

However, the immediate problem I have seems to come from the fact that
on Linux at least we're basically lying to configure about what's in the
system headers when we go to compile. port/linux.h on my system defined
_GNU_SOURCE which forces most/all of the extension things to be defined
even if they wouldn't by the command line options.  So, the compilation
sees different contents of the headers than configure did which means that
configure may say that something isn't defined, but it might be when
we go and compile.

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2003-09-26 15:10:42
Subject: Re: Fw: Case Insensitive Test
Previous:From: Tom LaneDate: 2003-09-26 14:52:13
Subject: Re: [ADMIN] postgres 6.2 vacuum

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