From: | John Gray <jgray(at)azuli(dot)co(dot)uk> |
---|---|
To: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Current CVS build fails in src/backend/utils/mb/conversion_procs (VPATH) |
Date: | 2002-08-05 17:21:54 |
Message-ID: | 1028568117.2014.47.camel@adzuki |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
I'd love to submit a patch for this, but I can't get my head round the
intricacies of the build system.
I'm building CVS from earlier today, and get the following errors:
make -C mb SUBSYS.o
make[4]: Entering directory
`/home/jgray/postgres/pgbuild2/src/backend/utils/mb'make[5]: Entering
directory
`/home/jgray/postgres/pgbuild2/src/backend/utils/mb/conversion_procs'
make[6]: Entering directory
`/home/jgray/postgres/pgbuild2/src/backend/utils/mb/conversion_procs/utf8_and_ascii'
Makefile:11: ../proc.mk: No such file or directory
make[6]: *** No rule to make target `../proc.mk'. Stop.
The file proc.mk is not found from the source tree, which I presume is
the problem
I can't just link across proc.mk because it seems to have other
dependencies. Also, I note in proc.mk at line 19:
include $(top_builddir)/src/Makefile.shlib
As the prep_buildtree script doesn't copy Makefile.shlib into the
buildtree, I assume this should really read:
include $(top_srcdir)/src/Makefile.shlib
--not that this helps either. I now get:
make[6]: Entering directory
`/home/jgray/postgres/pgbuild2/src/backend/utils/mb/conversion_procs/utf8_and_ascii'
make[6]: *** No rule to make target `utf8_and_ascii.o', needed by
`libutf8_and_ascii.so.0.0'. Stop.
Any suggestions (bearing in mind I am not a make expert at all!)
Regards
John
(configure options: --enable-debug --enable-depend
--enable-integer-datetimes --with-pgport=5433
GNU make: 3.79.1
--
John Gray
Azuli IT
www.azuli.co.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Peter A. Daly | 2002-08-05 17:22:20 | Re: [HACKERS] []performance issues |
Previous Message | scott.marlowe | 2002-08-05 17:01:37 | Re: Error: missing chunk number ... |