From: | David Hartwig <daveh(at)insightdist(dot)com> |
---|---|
To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
Cc: | hackers(at)postgreSQL(dot)org, scrappy(at)hub(dot)org |
Subject: | Re: [HACKERS] SPARC, SunOS 5.5.1, gcc 2.7.2.1 - can't compile... |
Date: | 1998-09-04 13:30:02 |
Message-ID: | 35EFEB5A.9B061DF5@insightdist.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Vadim Mikheev wrote:
> src/backend/port/snprintf.c:
>
> snprintf.c:84: structure has no member named `_flags'
> snprintf.c:84: `__SWR' undeclared (first use this function)
> snprintf.c:84: (Each undeclared identifier is reported only once
> snprintf.c:84: for each function it appears in.)
> snprintf.c:84: `__SSTR' undeclared (first use this function)
> snprintf.c:85: structure has no member named `_bf'
> snprintf.c:85: structure has no member named `_p'
> snprintf.c:86: structure has no member named `_bf'
> snprintf.c:86: structure has no member named `_w'
> snprintf.c:89: structure has no member named `_p'
> ^^^^^^^^^
> This is about FILE structure...
> BSD code was used for snprintf.c, but
> FILE in BSD is not the same as in SunOS 5.5.1...
I have the same problem on my AIX box. , Linux includes snprint as in the
stdio library.
I would prefer to drop snprintf altogether, and replace it with sprintf and a
sufficient buffer. The places where snprintf is used are logically bound to
string lengths less than 64 bytes. Otherwise, snprintf becomes another
porting issue. I have no idea how to ( or wheather I can) implement this
using vprintf. The flags and data structures are very different.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-09-04 14:22:48 | Re: [HACKERS] Subqueries? |
Previous Message | Metin Ozsavran | 1998-09-04 08:32:48 | Can PostgreSQL answer near-real-time demands? |