Re: headerscheck warnings with late-model gcc

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: headerscheck warnings with late-model gcc
Date: 2025-08-29 07:37:36
Message-ID: 5101ab7b-e38b-4c56-b8b1-38655a5ecd6a@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07.08.25 16:58, Tom Lane wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
>> Attached are three patches to fix some unrelated problems with
>> headerscheck in my environment.
>
> 0001 seems fine; it's an oversight that I'd not noticed because
> ICU_CFLAGS is empty in my usage.

committed

> Don't like 0002 as-is. I'd be okay with skipping that header if
> --with-llvm isn't given. However, we already tell users that
> they'd better configure --with-perl and --with-python, so maybe
> just add --with-llvm to that list?

Yes, just added documentation.

> 0003: +1, I noticed that too yesterday.

committed

> 0004: I prefer the solution I exhibited yesterday, ie add
> externs to those headers.

That solution seems fine, too.

This comment should be clarified:

+ # This redundant extern declaration is needed to silence headerscheck
+ # warnings with some gcc versions.

You could just write

# silence -Wmissing-variable-declarations

which also appears elsewhere in the code.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2025-08-29 07:41:56 Re: Adding REPACK [concurrently]
Previous Message m.korotkov 2025-08-29 07:36:22 Re: pg_dump: fix memory leak