>> ...is recompiling sasl with -fPIC actaully the correct course of action? Or >> is it >> libdb.a which needs to be recompiled with -fPIC instead? > >Yes, in this case you also have to recompile "db" with -fPIC.
Ah ha, recompiled db with -fPIC and got a bit further before a similar error, this time about libfsl.... so did the same with fsl - and volia, sasl sucessfully built! :) Unfortunatly my happiness was short lived, as imapd (imapd-2.2.12-2.3.0_kolab4.src.rpm), which was originally failing because it was dependant on sasl, still failed to build. This time the error was: Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.69920 + cd /kolab/RPM/TMP + cd cyrus-imapd-2.2.12 + cflags=-I/kolab/include + cflags='-I/kolab/include -DATVDOM=yes' + ldflags='-L/kolab/lib -L/kolab/lib' + case "amd64-linux2.6" in + loclibs= + case "amd64-linux2.6" in + CC=/kolab/bin/cc + CPPFLAGS='-I/kolab/include -DATVDOM=yes' + CFLAGS='-O2 -pipe -I/kolab/include -DATVDOM=yes' + LDFLAGS='-L/kolab/lib -L/kolab/lib' + LIBS='-lfsl -lnsl ' + ./configure --cache-file=./cache.config --prefix=/kolab --sysconfdir=/kolab/etc/imapd --with-openssl=/kolab --with-dbdir=/kolab --with- sasl=/kolab --with-statedir=/kolab/var/imapd --with-auth=unix --without-libwrap --with-perl --without-ucdsnmp --with-cyrus-prefix=/kolab -- with-cyrus-user=kolab-r --with-cyrus-group=kolab-r configure: creating cache ./cache.config checking build system type... Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized configure: error: /bin/sh ./config.sub x86_64-unknown-linux-gnu failed error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.69920 (%build) Is there anything I can do about this? I can't beleive imapd wont build on AMD64! Once again, thanks for all you help, Andy ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org
