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

Re: Third email on compilining 7.0.2 on Solaris 2.5.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ghaverla(at)freenet(dot)edmonton(dot)ab(dot)ca
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Third email on compilining 7.0.2 on Solaris 2.5.1
Date: 2000-08-19 04:39:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
ghaverla(at)freenet(dot)edmonton(dot)ab(dot)ca writes:
>> Dunno why src/include/c.h is not including that automatically on your
>> platform, but that's what to look at.

> I found that out some time today.

FWIW, in current sources <stdarg.h> is included *unconditionally* by
c.h, so your problem should go away in 7.1.  (This may mean that any
remaining not-quite-ANSI platforms will crash and burn ...)  In the
meantime you might check how things work for you if you change c.h to
include <stdarg.h> unconditionally.

>> I've suspected for some time that the conditional include of <varargs.h>
>> near the bottom of c.h is dead code, if not actively pernicious.  But
>> without access to a platform where
>> #if defined(sun) && defined(__sparc__) && !defined(__SVR4)
>> applies, I can't be sure whether to rip it out or not.

> Well, I have a Sun Ultra Enterprise 2 (2 166 MHz UltraSPARCs)
> running Solaris 2.5.1.  If that qualifies as one of these
> platforms, ...

Evidently not, else your hand addition of <varargs.h> wouldn't have
changed anything since it'd already have been included.  I'm guessing
that your compiler predefines __SVR4.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Paulo Roberto SiqueiraDate: 2000-08-19 23:29:43
Subject: Triggers?
Previous:From: ghaverlaDate: 2000-08-19 04:27:41
Subject: Re: Third email on compilining 7.0.2 on Solaris 2.5.1

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