Richard
First a small note, we are not replacing the SASL that is included in the system by Apple. We are just providing the right include files and libraries that we need later on. You’ll need to get the source code from Carnegie Mellon off their FTP server, get cyrus-sasl-2.1.22.tar.gz from their server. Get this version and not a later one, I haven’t got the later versions to compile properly on my machine and didn’t have the time to check why. Perhaps later when I got some more spare time I’ll check why.
Before we start building SASL, you need to check to see if ‘/usr/include/pam‘ has been symlinked to ‘/usr/include/security‘ and if not, symlink it using this command line:
Unpack the source code and use the terminal, go to the directory in which you unpacked the source and issue the following commands as a normal user:
For Intel
./configure
For PowerPC
./configure
Continue with:
And then install with command:
Cyrus SASL is installed in ‘/usr/local/lib/sasl2‘ by default, and wants to by symlinked to ‘/usr/lib/sasl2‘. We are going to use Apple’s libraries instead of the Cyrus distribution, so ignore the symlink request. The last step we need to do here is:
This enables a couple of useful plug-ins that Apple had turned off and we will need later on.
Next step: Building the Postfix mailserver
Comments
8:46 pm
Trying to install SASL
(cd . && ln -s sasldb.lo sasldb.o)
(cd . && ln -s sasldb_init.lo sasldb_init.o)
(cd . && ln -s plugin_common.lo plugin_common.o)
../libtool: line 1: test: too many arguments
gcc -bundle -undefined error -o .libs/libsasldb.2.0.8.so sasldb.lo sasldb_init.lo plugin_common.lo -all_load ../sasldb/.libs/libsasldb.al -L/usr/local/lib -lresolv -lresolv -lresolv -lresolv -lc -install_name /usr/lib/sasl2/libsasldb.2.so
powerpc-apple-darwin8-gcc-4.0.1: -install_name only allowed with -dynamiclib
make[2]: *** [libsasldb.la] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
I have no clue to what the problem is, can anyone help?
9:01 pm
Send email, please answer…
2:37 am
Hi Richard,
I think you left out a step here. I noticed this when I rebuilt my mail server on my Tiger server. If ‘/usr/local/lib/sasl2′ is symlinked to ‘/usr/lib/sasl2′, then ‘/usr/lib/sasl2′ has to be moved to something like ‘/usr/lib/sasl2.backup’ first otherwise the symlink won’t work properly or you’ll overwrite the ‘/usr/lib/sasl2′ directory so you won’t be able to copy the disabled files.
Markis
7:11 am
@Markus, the symlink is not needed. You need to ignore the sylink request and continue.
9:46 am
Oh, mine never asked to be symlinked so I thought I had to do that manually. Nevermind.
Markis