Re: v13 latest snapshot build error - Mailing list pgsql-hackers

From Devrim Gunduz
Subject Re: v13 latest snapshot build error
Date
Msg-id E4A5FE31-8A46-4A8B-BEA6-2DB4AF67BCD8@gunduz.org
Whole thread Raw
In response to Re: v13 latest snapshot build error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: v13 latest snapshot build error  (Devrim Gündüz <devrim@gunduz.org>)
List pgsql-hackers
Hi,

(Sorry for top posting)

This happens on RHEL 8. I don't think it's that bleeding edge.

Regards, Devrim

On 11 March 2020 19:44:55 GMT, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Devrim Gündüz <devrim@gunduz.org> writes:
I'm getting build error while building latest snapshot. Any idea why? Please
note that I'm adding this patch to the tarball:
https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/master/postgresql-13/master/postgresql-13-var-run-socket.patch;h=a0292a80ae219b4c8dc1c2e686a3521f02b4330d;hb=HEAD

(Hey, I recognize that patch ...)

In file included from ../../../../src/include/c.h:55,
from ../../../../src/include/postgres.h:46,
from guc.c:17:
../../../../src/include/pg_config_manual.h:200:31: error: called object is not
a function or function pointer
#define DEFAULT_PGSOCKET_DIR "/var/run/postgresql"
^~~~~~~~~~~~~~~~~~~~~
guc.c:4064:3: note: in expansion of macro 'DEFAULT_PGSOCKET_DIR'
DEFAULT_PGSOCKET_DIR ", /tmp"
^~~~~~~~~~~~~~~~~~~~
make[4]: *** [<builtin>: guc.o] Error 1

That is just weird. Could it be a compiler bug? I assume you're
using some bleeding-edge gcc version, and it's really hard to see
another reason why this would fail, especially with a nonsensical
error like that.

regards, tom lane

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add an optional timeout clause to isolationtester step.
Next
From: Alvaro Herrera
Date:
Subject: Re: control max length of parameter values logged