| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: buildfarm failure in XML code |
| Date: | 2007-02-16 15:09:14 |
| Message-ID: | 27378.1171638554@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Freitag, 16. Februar 2007 14:59 schrieb Alvaro Herrera:
>> UX:acomp: ERROR: "xml.c", line 2188: undefined symbol: INT64_MAX
>> UX:acomp: ERROR: "xml.c", line 2188: undefined symbol: INT64_MIN
>>
>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=warthog&dt=2007-02-1
>> 6%2009:06:01
> It needs a rebuild after the fix.
This "fix" doesn't fix anything. We have always in the past managed to
avoid assuming that int64 actually is available; I don't intend to give
the xml code a free pass to break that, especially for such an utterly
marginal purpose as this code has. I'm also wondering why xml.c is the
only place anywhere in the code that uses <stdint.h>.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-02-16 15:33:31 | Re: buildfarm failure in XML code |
| Previous Message | Seneca Cunningham | 2007-02-16 15:02:42 | Intermittent buildfarm failures due to timestamptz test |