Thanks for reporting this! I'll get it fixed in the next version. -- Sam Clippinger
Iavor Stoev wrote: > Hello, > > I've tried to install spamdyke 4.0.10 compilled against the OpenSSL > library residing in a non standard path. > > Fortunately the configure script of spamdyke is offering such a option: > > Some influential environment variables: > CC C compiler command > CFLAGS C compiler flags > LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a > nonstandard directory <lib dir> > LIBS libraries to pass to the linker, e.g. -l<library> > CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> > if you have headers in a > nonstandard directory <include dir> > CPP C preprocessor > > > The configure script is advertising that I have to use the CPPFLAGS > variable to include a custom include dir. But the Makefile.in doesn't > use the CPPFLAGS at all. > > So the solution is to use the configure like this: > > CPPFLAGS="-I/usr/local/ssl/include" LDFLAGS="-L/usr/local/ssl/lib" > ./configure > > And then I have to manualy edit the Makefile and add > "-I/usr/local/ssl/include" to CFLAGS variable. > > It is a pritty minor bug anyway, but the spamdyke software (config > documentation, source) is with very good quality and I think that this > small bug should be addressed also :) > > Best Regards > > Iavor Stoev - Senior System Administrator > ICDSoft Ltd - http://icdsoft.com > _______________________________________________ > spamdyke-dev mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-dev > _______________________________________________ spamdyke-dev mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-dev
