Home > Archive > Slony1 PostgreSQL Replication > January 2006 > Build oddities in RC3









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Build oddities in RC3
Philip Yarra

2006-01-12, 3:25 am

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=$SLONBIND
IR

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.
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com