Re: OSF build broken
От
Kurt Roeckx
Тема
Re: OSF build broken
Дата
Msg-id
20030707063041.GA18871@ping.be
Ответ на
Re: OSF build broken (Tom Lane)
Список
Дерево обсуждения
OSF build broken Philip Yarra <philip@utiba.com>
Re: OSF build broken Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build broken Stephan Szabo <sszabo@megazone23.bigpanda.com>
Re: OSF build broken Philip Yarra <philip@utiba.com>
Re: OSF build broken Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build broken Philip Yarra <philip@utiba.com>
Re: OSF build broken Joe Conway <mail@joeconway.com>
Re: OSF build broken Philip Yarra <philip@utiba.com>
Re: OSF build broken Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build broken Kurt Roeckx <Q@ping.be>
Re: OSF build broken Philip Yarra <philip@utiba.com>
Re: OSF build broken Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build fixed Philip Yarra <philip@utiba.com>
Re: OSF build fixed Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build fixed Kurt Roeckx <Q@ping.be>
Re: OSF build fixed Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build fixed Kurt Roeckx <Q@ping.be>
Re: OSF build fixed Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build fixed Kurt Roeckx <Q@ping.be>
Re: OSF build fixed Tom Lane <tgl@sss.pgh.pa.us>
Re: OSF build fixed Kurt Roeckx <Q@ping.be>
Re: OSF build fixed Philip Yarra <philip@utiba.com>
On Mon, Jul 07, 2003 at 01:46:21AM -0400, Tom Lane wrote: > Philip Yarra writes: > > And on RedHat 7.3 it's in stdint.h - they must move it around to keep the > > snipers guessing. > > Sometimes it seems that way :-( > > > What's the best (most portable) way to fix this? > > My vote is to rip out every last reference to int64_t and other > system-header-dependent datatypes. These were added in the recent > IPv6 changes, and I thought at the time that they'd not stand the > test of portability, but I kept quiet for lack of evidence. Now > there is some. I recommend sending in a patch that replaces int64_t > with int64, and likewise for anything you don't see defined or used > in src/include/c.h. The stuff in c.h has been through the wars > already, the IPv6 code has not. I used int64_t because that's standard (C99). But int64 will do too. Kurt
В списке pgsql-hackers по дате отправления