Wed Jan 11 21:02:23 PST 2006
- Previous message: [Slony1-general] unable to remove stale pg_listener entries
- Next message: [Slony1-general] RC3 Available?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi folks, just noticed that RC3 build seems to insist on installing slon and
slonik in /usr/bin. This is despite the ./configure default of /usr/local,
and even happens if you explicitly tell it where to install with ./configure
--prefix=/usr/local:
make[2]: Entering directory `/tmp/slony1-1.1.5-rc3/src/slon'
/bin/sh /tmp/slony1-1.1.5-rc3/config/mkinstalldirs /usr/bin/
/bin/sh /tmp/slony1-1.1.5-rc3/config/install-sh -c -m 755 slon /usr/bin/
make[2]: Leaving directory `/tmp/slony1-1.1.5-rc3/src/slon'
make[2]: Entering directory `/tmp/slony1-1.1.5-rc3/src/slonik'
/bin/sh /tmp/slony1-1.1.5-rc3/config/mkinstalldirs /usr/bin/
/bin/sh /tmp/slony1-1.1.5-rc3/config/install-sh -c -m 755 slonik /usr/bin/
I do have PostgreSQL 8.1.1 installed from RPMs, though can't see that this
would affect configure.
In Makefile.global, prefix is /usr/local, but slonbindir is /usr/bin. I think
the cause is this (in configure):
#-- if test ${prefix} = "NONE"; then
SLONBINDIR="${PG_BINDIR}"
#-- else
#-- SLONBINDIR="${prefix}/bin"
#-- fi
SLONBINDIR=$SLONBINDIR
I'm guessing this is a bug?
Regards, Philip.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
- Previous message: [Slony1-general] unable to remove stale pg_listener entries
- Next message: [Slony1-general] RC3 Available?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list