Summary: | --prefix and --exec-prefix options don't function as expected | ||
---|---|---|---|
Product: | Slony-I | Reporter: | Tom Lippincott <tom.lippincott> |
Component: | core scripts | Assignee: | Christopher Browne <cbbrowne> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | slony1-bugs |
Priority: | low | ||
Version: | devel | ||
Hardware: | PC | ||
OS: | Linux |
Description
Tom Lippincott
2009-04-03 15:23:17 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. 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. I'll see about adding this to the documentation. Added better documentation to HEAD: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=7a6791501014799adc8a0bb7c2c9692777cc24a5 Also, cherry-picked into 2.0 branch: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commit;h=4ed4d80546db1c5d9fd9c82caaa546ef2eeee0e0 |