Hi Philip,
On Mon, 24 Oct 2005, Philip Yarra wrote:
Hi all, I've been looking to install and test Slony 1.1.2 from RPMs on the
RedHat ES3.0 machines here. I see there are RPMs for SuSE and Fedora Core 4
at http://developer.postgresql.org/~devrim/slony/1.1.2/ but none for RH
ES3.0, so I figured I'd grab the SRPMs and build them myself.
Yeah, I had no time to build RPMs for for RHEL3. Will do it later today.
There are only SRPMs for SuSE and Fedora Core 4, so I grabbed the FC4 one
(assumed that was closest to RedHat ES.0 of the two).
SRPM suits all Red Hat'ish platforms.
It's taken a bit of doing, as the build (using FC4 spec file) doesn't look
in /usr/kerberos/include for krb5.h:
make[2]: Entering directory
`/home/philip/rpm/BUILD/postgresql-slony1-engine-REL_1_1_2/src/slonik'
gcc -O2 -g -pipe -march=i586 -I/usr/include/et -I../.. -I/usr/include/
-I/usr/include/pgsql/server/ -DPGSHARE="\"/usr/share/pgsql/\""
-DSED="\"sed\"" -I/usr/include/ -I/usr/include/pgsql/server/ -I/usr/include/
-I/usr/include/pgsql/server/ -I/usr/include/ -I/usr/include/pgsql/server/
-I/usr/include/et -c -o slonik.o slonik.c
In file included from /usr/include/openssl/ssl.h:179,
from /usr/include/libpq-fe.h:33,
from slonik.c:26:
/usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory
This is/was a bug of RHEL 3 and it was fixed in newer versions. Here is
quick solution to solve your problem:
[EMAIL PROTECTED] root]# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 3 (Taroon Update 6)
[EMAIL PROTECTED] root]# ll /usr/include/krb5.h
lrwxrwxrwx 1 root root 28 Feb 14 2005
/usr/include/krb5.h -> /usr/kerberos/include/krb5.h
That's what I did on most of my RHEL 3 boxes.
The RedHat spec file included in the 1.1.2 tarball doesn't seem to have the
fixes mentioned here:
http://gborg.postgresql.org/pipermail/slony1-general/2005-October/003105.html
and in any case, that doesn't look in /usr/kerberos/include either.
That's weird. I've committed the fixes to RH spec file before 1.1.2 was
released. :( The CVS version does not include those bugs.
Use
make rpm
to build RPMs...
I ended up hacking in '-I/usr/kerberos/include' for CFLAGS and CPPFLAGS (as
that is how com_err.h gets pulled in) and the build succeeds. But is that the
correct procedure? Or is there some --define invocation I should be using
instead?
See above.
PS: I also ended up having to build without docs, as they failed in colourful
ways, which I will detail seperately if people think it's worthwhile
See the INSTALL file for the details of this.
Regards,
--
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
