Hi all,

When --disable-dso is added to ./configure, the DBD and crypto modules aren't 
added to the linking step, and are neither built nor linked. As a result, an 
attempt to load the library fails with missing symbols from the loadable 
modules.

I've been trying to pick apart configure.in and dso.m4, but haven't found any 
obvious reason for this yet. Does this ring a bell with anyone?

Regards,
Graham
--

Reply via email to