From: | Martin Pitt <martin(at)piware(dot)de> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: horology regression test failure |
Date: | 2005-12-21 08:38:12 |
Message-ID: | 20051221083812.GA5789@piware.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Hi!
Tom Lane [2005-12-20 17:16 -0500]:
> Martin Pitt <martin(at)piware(dot)de> writes:
> > ./configure --libdir=3D/usr/lib/postgresql/8.1/lib --bindir=3D/usr/lib/pos=
> > tgresql/8.1/bin
>
> > is enough to reproduce the problem. With only --libdir, it works, and
> > with only --bindir the test suite does not run at all because the
> > postmaster cannot find $libdir (but that is still justifiable).
>
> Try adding --datadir=/usr/lib/postgresql/8.1/share to that. Actually,
> you'd be best off replacing all three options with
> --prefix=/usr/lib/postgresql/8.1
> because that will make sure that the entire installation is consistent.
When I only specify --prefix, it indeed works. However, it already
breaks again with
./configure --prefix=/usr/share/postgresql/8.1 --exec-prefix=/usr/lib/postgresql/8.1
I'm fine with dropping --bindir, --libdir, --datadir, but at least the
arch-independent and arch-dependent prefix should work. I do not want
to put all arch-independent data into /usr/lib, it would violate the
FHS and Debian Policy.
Is it possible to fix this?
Thanks,
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
In a world without walls and fences, who needs Windows and Gates?
From | Date | Subject | |
---|---|---|---|
Next Message | Sagi Bashari | 2005-12-21 12:18:51 | BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding conversion |
Previous Message | Martin Pitt | 2005-12-21 07:21:27 | Re: horology regression test failure |
From | Date | Subject | |
---|---|---|---|
Next Message | Anna Domachowska | 2005-12-21 10:01:38 | problem with nasty latin2 sorting |
Previous Message | Hannu Krosing | 2005-12-21 07:50:03 | Re: status of concurrent VACUUM patch ... |