Re: [HACKERS] SPARC, SunOS 5.5.1, gcc 2.7.2.1 - can't compile...
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] SPARC, SunOS 5.5.1, gcc 2.7.2.1 - can't compile... |
Дата | |
Msg-id | 199809041429.KAA01737@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] SPARC, SunOS 5.5.1, gcc 2.7.2.1 - can't compile... (David Hartwig <daveh@insightdist.com>) |
Список | 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. Agreed. -- Bruce Momjian | 830 Blythe Avenue maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026 + If your life is a hard drive, | (610) 353-9879(w) + Christ can be your backup. | (610) 853-3000(h)
В списке pgsql-hackers по дате отправления: