On February 26, 2004, Ken Hornstein <[EMAIL PROTECTED]> wrote: > >Hmm. Okay, I see, /usr/include/sasl.h is the 1.5 version of the header, and > >/usr/include/sasl/sasl.h is the 2.1 version. I presume this happens if you > >install Cyrus 2.1 with some kind of 1.x compatibility turned on or > >something? > > No, definately not. There's no compatibility for the old SASL API. > Is there a /usr/lib/libsasl.* ? This sounds like a RedHat-ism.
www-dan> ls -oF /usr/lib/libsasl* -rw-r--r-- 1 root 62474 Jan 25 2003 /usr/lib/libsasl.a -rwxr-xr-x 1 root 770 Jan 25 2003 /usr/lib/libsasl.la* lrwxrwxrwx 1 root 17 Feb 23 09:44 /usr/lib/libsasl.so -> libsasl.so.7.1.11* lrwxrwxrwx 1 root 17 Feb 23 03:39 /usr/lib/libsasl.so.7 -> libsasl.so.7.1.11* -rwxr-xr-x 1 root 43612 Jan 25 2003 /usr/lib/libsasl.so.7.1.11* -rw-r--r-- 1 root 259634 Jan 25 2003 /usr/lib/libsasl2.a -rwxr-xr-x 1 root 768 Jan 25 2003 /usr/lib/libsasl2.la* lrwxrwxrwx 1 root 18 Feb 23 09:44 /usr/lib/libsasl2.so -> libsasl2.so.2.0.10* lrwxrwxrwx 1 root 18 Feb 23 03:39 /usr/lib/libsasl2.so.2 -> libsasl2.so.2.0.10* -rwxr-xr-x 1 root 76612 Jan 25 2003 /usr/lib/libsasl2.so.2.0.10* > >Otherwise, some autoconf support will be necessary. > > Since you can specify CPPFLAGS=-I/usr/include/sasl, I don't think it's > critical right now. I'd really rather push 1.1 out the door at this > stage, since it's been so delayed. As I mentioned, I set that and it had no effect. There appears to be a bug in the nmh makefiles with propagating the CPPFLAGS setting. I believe I saw it get passed down to make as it recursed into directories, but the setting didn't get used on the compile commandline. I can go in and manually compile the files that bomb, adding -I/usr/include/sasl, but I don't think most would be so patient, and Red Hat isn't exactly an uncommon OS... -- Dan Harkless http://harkless.org/dan/ _______________________________________________ Nmh-workers mailing list [EMAIL PROTECTED] http://mail.nongnu.org/mailman/listinfo/nmh-workers
