Remko van der Vossen writes:
Thanks for the response, and sorry for the delay.The system is not old, as you can see from the package versions. The system is not using PAM on purpose. I checked which crypt libcourierauthcommon.so links to (/lib/libcrypt.so.1) and checked the functionality of that crypt with a short test program. Crypt is returning me a proper encrypted version of the key. I do however need to #define _XOPEN_SOURCE, to enable crypt as per man crypt. If I do not supply this #define I get a sigsegv. Could it be that courier does not specify this #define where it uses crypt? And if not, should it?
No, generic source code, in general, is not going to specify platform- specific requirements. Some of this compatibility stuff is handled by autoconf, but not in every case.
If you need some custom flag to compile the code, the establish procedure for doing so is to explicitly specify it, when you build it.
Specifically, pass the CPPFlAGS='-D_XOPEN_SOURCE=1' parameter to the configure script, see configure --help
pgp6286ttR_6U.pgp
Description: PGP signature
------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
