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

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

[Adding Christoph]

On Wed, 2020-03-11 at 21:07 +0000, Devrim Gunduz wrote:
> This happens on RHEL 8. I don't think it's that bleeding edge.

Morever, my RHEL 7 build are broken as well:

+ MAKELEVEL=0
+ /usr/bin/make -j4 all
In file included from /usr/include/time.h:37:0,
                 from ../../../../src/include/portability/instr_time.h:64,
                 from ../../../../src/include/executor/instrument.h:16,
                 from ../../../../src/include/nodes/execnodes.h:18,
                 from ../../../../src/include/executor/execdesc.h:18,
                 from ../../../../src/include/executor/executor.h:17,
                 from ../../../../src/include/commands/explain.h:16,
                 from ../../../../src/include/commands/prepare.h:16,
                 from guc.c:40:
guc.c:4068:3: error: called object is not a function or function pointer
   NULL, NULL, NULL
   ^
make[4]: *** [guc.o] Error 1
make[3]: *** [misc-recursive] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [utils-recursive] Error 2
make[1]: *** [all-backend-recurse] Error 2
make: *** [all-src-recurse] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.PXbYKE (%build)
    Bad exit status from /var/tmp/rpm-tmp.PXbYKE (%build)

IDK what is going on, but apparently something is broken somewhere.

Cheers,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Refactor compile-time assertion checks for C/C++
Next
From: Tom Lane
Date:
Subject: Re: v13 latest snapshot build error