Bug 79 - --prefix and --exec-prefix options don't function as expected
Summary: --prefix and --exec-prefix options don't function as expected
Status: RESOLVED FIXED
Alias: None
Product: Slony-I
Classification: Unclassified
Component: core scripts (show other bugs)
Version: devel
Hardware: PC Linux
: low minor
Assignee: Christopher Browne
URL:
Depends on:
Blocks:
 
Reported: 2009-04-03 15:23 UTC by Tom Lippincott
Modified: 2010-08-16 14:26 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Lippincott 2009-04-03 15:23:17 UTC
The makefile doesn't respect the prefix variables correctly:

mkdir ~/temp
./configure --prefix=/usr/local --exec-prefix=/usr/local
make
make install DESTDIR=~/temp
ls ~/temp/usr
  lib64  local  share

This is important functionality to get right, for those of us looking to keep custom software under a single hierarchy, since its not included in official repositories.



On an unrelated note, the spec-file in the release fails with:

configure.ac:89: error: AC_SUBST: `2.0.1' is not a valid shell variable name
configure.ac:89: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
error: Bad exit status from /var/tmp/rpm-tmp.CLmZ2P (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.CLmZ2P (%build)
Comment 1 Christopher Browne 2009-04-09 14:58:11 UTC
I presume that you were running autoconf 2.63?  It appears that there was a change to autoconf recently that induces this.  It is eminently unclear, from the bug reports out there, what the *real* issue is.

It's complaining about the substitution of AC_SUBST(SLONREL_VERSION), and I don't see any references to SLONREL_VERSION outside of configure.ac, so it appears safe to drop out that substitution.

I have committed that change to 2.0 + HEAD.
Comment 2 Jan Wieck 2010-08-13 21:13:27 UTC
The currently correct way IMHO is to use neither of those options at all, but instead invoke configure as

./configure --with-pgconfigdir=<path-to-desired-pg-bin-dir> ...

The only other options given here should be things like --with-docs and the like, that only affect what is built.

Slony-I highly depends on having its stuff installed in what the backend thinks $libdir is. Using pg_config is your best bet to get that right.

This is probably a documentation issue.
Comment 3 Christopher Browne 2010-08-16 14:08:16 UTC
I'll see about adding this to the documentation.