Building storage/lwlocknames.h? - Mailing list pgsql-hackers

Hi,

the Debian package build compiles plpython twice, once for python 2 in
the main build, and then for python 3 in an extra run. In order not to
waste too much time, we have this recipe in there:

stamp/build-py3: stamp/configure-build-py3       $(MAKE) -C build-py3/src/backend/ submake-errcodes       $(MAKE) -C
build-py3/src/pl/plpython      $(MAKE) -C build-py3/contrib/hstore_plpython
 

So far that worked, but on 9.6 head there's now a problem with
storage/lwlocknames.h:

18:20:02 gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels
-Wmissing-format-attribute-Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2
-fstack-protector-strong-Wformat -Werror=format-security -I/usr/include/mit-krb5 -fPIC -pie -fno-omit-frame-pointer
-fpic-I. -I/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/pl/plpython -I/usr/include/python3.4m
-I../../../src/include-I/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include
-D_FORTIFY_SOURCE=2-D_GNU_SOURCE   -c -o plpy_cursorobject.o
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/pl/plpython/plpy_cursorobject.c
18:20:02 In file included from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/storage/lock.h:23:0,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/access/heapam.h:22,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/nodes/execnodes.h:18,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/executor/execdesc.h:18,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/utils/portal.h:50,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/executor/spi.h:18,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/pl/plpython/plpy_planobject.h:8,
18:20:02                  from
/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/pl/plpython/plpy_cursorobject.c:18:
18:20:02 /tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/../src/include/storage/lwlock.h:96:33: fatal
error:storage/lwlocknames.h: No such file or directory
 
18:20:02 compilation terminated.
18:20:02 <builtin>: recipe for target 'plpy_cursorobject.o' failed
18:20:02 make[2]: *** [plpy_cursorobject.o] Error 1
18:20:02 make[2]: Leaving directory '/tmp/buildd/postgresql-9.6-9.6~~devel~20150916.1605/build-py3/src/pl/plpython'

Can we have a "submake-lwlocknames" build target like there already is
for submake-errcodes? Reading the Makefile I could not see how to
manually trigger this individually.

Thanks,
Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/