| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(at)vondra(dot)me>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Japin Li <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Cannot find a working 64-bit integer type on Illumos |
| Date: | 2025-09-04 09:05:03 |
| Message-ID: | 57d8ee4f-8c96-410b-9b9c-8f38076a5ba0@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2025-09-04 09:50:38 | Re: Refactoring: Use soft error reporting for *_opt_error functions |
| Previous Message | Peter Eisentraut | 2025-09-04 09:01:37 | Re: Cannot find a working 64-bit integer type on Illumos |