[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Hi all,
>
> > -----Original Message-----
> > From: owner-pgsql-general@postgreSQL.org
> > [mailto:owner-pgsql-general@postgreSQL.org]On Behalf Of Bruce Momjian
> > Sent: Thursday, December 24, 1998 6:14 AM
> > To: Adriaan Joubert
> > Cc: riches@ms.washington.edu; pgsql-general@postgreSQL.org
> > Subject: Re: [GENERAL] Postgres 6.4.1 on DEC-ALPHA
> >
> >
> > > I managed to compile postgres 6.4.1 without too much hassle, with the
> > > following
> > >
> > > ./configure --with-CC=cc --without-CXX
> > >
> > > There was only a single problem in
> > >
> > > /data/build/pgsql/src/backend/port/snprintf.c
> > >
> > > where around line 120 it should read
> > >
> > >
> > > #ifndef HAVE_LONG_INT_64
> > > static void fmtnum __P((long_long value, int base, int dosign,
> > int ljust,
> > > int le
> > > n, int zpad));
> > > #else
> > > static void fmtnum __P((long value, int base, int dosign, int ljust, int
> > > len, in
> > > t zpad));
> > > #endif
> >
>
> On my platform(Solaris 2.51 x86),I also have the same problem.
> And moreover there is another problem.
>
> On my platform,type long long exists and the following step
>
> unsigned long_long uvalue;
>
> causes compilation error(gcc version is 2.7.2.3). long_long is
> typedef'd and unsigned (typedef) is out of specification ?
Yes, you have found two problems. HAVE_LONG should have been
HAVE_LONG_LONG, and you can't unsigned a typedef. I have applied fixes
for both of these.
This long long stuff was clearly broken, but now that we have configure
properly recognizing it, the snprint stuff is showing our problems.
Looks like we will need a patch for these problems.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
