From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: submake-errcodes |
Date: | 2018-04-12 18:36:00 |
Message-ID: | 10354.1523558160@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
> ... still same error. Easy to reproduce on F-27 box.
I don't have F27 at hand, but I tried F26 and F28, and I can't reproduce
on either one. I tried various combinations of python2 versus python3,
in-tree build versus VPATH from bare checkout versus VPATH from
distprep'd tree, and they all work for me.
Just to clarify, I'm experimenting with
$ git clean -dfx
$ ./configure ... --with-python [ PYTHON=/usr/bin/python3 ]
$ cd src/pl/plpython/
$ make -j25
and variants of that, and what I get as a result is a make trace
starting with
make -C ../../../src/backend generated-headers
If you're not seeing that, something's very wrong, and I do not
know what.
[ time passes ]
... or then again, maybe I do. Is it possible that your build
recipe involves invoking our makefiles from an outer "make" run?
If so, maybe you need to explicitly set MAKELEVEL=0 when invoking
our build, to keep it from thinking it is a sub-make. Not sure
about whether it'd be wise to reset MAKEFLAGS as well.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2018-04-12 18:36:16 | Re: Native partitioning tablespace inheritance |
Previous Message | Alvaro Herrera | 2018-04-12 18:25:25 | Re: crash with sql language partition support function |