Re: Cannot find a working 64-bit integer type on Illumos - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Cannot find a working 64-bit integer type on Illumos
Date
Msg-id 57d8ee4f-8c96-410b-9b9c-8f38076a5ba0@eisentraut.org
Whole thread Raw
In response to Re: Cannot find a working 64-bit integer type on Illumos  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On 04.09.25 02:39, Thomas Munro wrote:
> Hmm.  So we're talking about a Debian system compiling an extension
> that has these headers in its search path:
> 
> /usr/include/postgresql/postgres_ext.h <-- v18[1]
> /usr/include/postgresql/17/server/postgres_ext.h <-- v17[2] (or other
> older release)
> 
> I guess it's only a problem if the v17 header is found first, but such
> an extension must build OK if the libpq headers are found first,
> right?  I'm not sure what to think about that yet, ie how to decide
> which orders should work.

The logs I have seen have the libpq include path first.

I don't think the order matters.  The problem is that you have two 
conflicting typedefs of the same name in two separate header files.  So 
if you include both of them, you'll get an error.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Cannot find a working 64-bit integer type on Illumos
Next
From: Dean Rasheed
Date:
Subject: Re: Refactoring: Use soft error reporting for *_opt_error functions