Am Samstag, den 10.12.2005, 01:19 +0100 schrieb Peter Eisentraut: > I think the postgresql-server-dev packages should not need libpq-dev at > all, at least for the header files. (I think the reason for the > dependency might be something to do with pg_config.) At least if you > compile a server-side module, you should be able to compile that using > only -I$(pg_config --includedir-server), which does not refer to any > libpq-dev files. > > I agree that the dependency is at least weird, if not a bug, but could > you provide an example where an actual build failure happens because of > this?
Well, the failure in the Sparc build produced the errors that I
recognized:
make[1]: Entering directory `/usr/local/src/slony1-1.1.2/src'
make[2]: Entering directory `/usr/local/src/slony1-1.1.2/src/xxid'
gcc -g -O2 -fpic -I../.. -I/usr/include/postgresql/
-I/usr/include/postgresql/8.0/server/ -c -o xxid.o xxid.c
In file included
from /usr/include/postgresql/8.0/server/nodes/relation.h:19,
from /usr/include/postgresql/8.0/server/executor/spi.h:23,
from xxid.c:20:
/usr/include/postgresql/8.0/server/nodes/parsenodes.h:547: error: syntax
error before 'AclId'
/usr/include/postgresql/8.0/server/nodes/parsenodes.h:547: warning: no
semicolon at end of struct or union
/usr/include/postgresql/8.0/server/nodes/parsenodes.h:548: warning: data
definition has no type or storage class
In file included
from /usr/include/postgresql/8.0/server/access/tupdesc.h:18,
...
Actually it libpq-dev makes it difficult, as the pg_config it supplies
gives a 8.1 version number, so you to specify additional options to
configure.
Basically I consider postgresql-server-dev-8.0 to depend upon 8.1
libpq-dev a bug. Two different sets of headers, that do not match.
The compilation errors go away when I install a libpq-dev based on
8.0(.3) from Ubuntu, but it won't link. And it doesn't want to load into
the server either.
I know the PostgreSQL maintainer considers 8.0 to be deprecated, but
there are still 8.0 packages available, AND upgrading a database server
is not a trivial thing in many cases. Even if I'd be at liberty to
upgrade the db server, I might need the ability to compile tools like
slony to faciliate the upgrade. So it's a showstopper bug, and I think
it's cause for the sparc build bug reported. (I guess you built it with
an 8.0 libpq-dev installed, while the sparc box had a new libpq-dev
based on 8.1 installed)
Andreas
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
