[Mod_log_sql] Installation problems on Mac OS X
urkle at outoforder.cc
Wed Jul 14 02:33:21 EST 2004
On Wed, 2004-07-14 at 02:07, Clay Loveless wrote:
> On 7/13/04 8:18 PM Pacific Time, Edward Rudd (urkle at outoforder.cc) wrote:
> Would it make a difference what version of MySQL libraries I have installed?
> I've got 4.1.3 libraries in place, which again, have been pulled in and used
> by a PHP build today without incident.
I've only tested the code with 3.23.x and 4.0.x, but it should work with
> *** Warning: linker path does not have real file for library -lmysqlclient.
> *** I have the capability to make that library automatically link in when
> *** you link to this library. But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libmysqlclient and none of the candidates passed a file format test
> *** using a file magic. Last file checked:
> *** Warning: libtool could not satisfy all declared inter-library
> *** dependencies of module mod_log_sql_mysql. Therefore, libtool will
> *** a static module, that should work as long as the dlopening
> *** application is linked with the -dlopen flag.
This huge paragraph above, That's the "warning/error" I was looking for.
that explains exactly why there is no .so for the mysql module.. it
seems as though your mysql install does not have shared client libraries
installed, or has them in some other place that libtool couldn't find..
If they are installed make sure that path is added to LDFLAGS in the
Edward Rudd <urkle at outoforder.cc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.outoforder.cc/pipermail/mod_log_sql/attachments/20040714/d6ff655f/attachment.bin
More information about the Mod_log_sql