newLISP, mysql and Fedora(and likely RedHat, etc.)

[ehrichweiss]

One of my first times playing with newLISP I discovered that there is a bit of a "bug" when using mysql. It would always return an error code telling me it couldn't find libmysqlclient.so despite the fact that I have it installed. I had looked at the paths in mysql.lsp several times before I discovered the problem: Fedora has it at /usr/lib/mysql/libmysqlclient.so which looks an awful lot like the /usr/mysql/lib/libmysqlclient.so listed.



Any chance someone wants to add that to the path list and commit it? I imagine it will cause a few of us some problems.

[Lutz]

Thanks, the path will be added / corrected.

[Ishpeck]

Noticed a similar problem on my OpenBSD 4.9 system.  



/usr/local/share/newlisp-10.2.16/modules/mysql.lsp had a line like...

Code Select Expand

"/usr/local/lib/libmysqlclient.so.19.0" ; OpenBSD 4.6

I changed it like so:

Code Select Expand

"/usr/local/lib/libmysqlclient.so.20.0" ; OpenBSD 4.9

And now it works.   You'd think the package maintainers would'a caught that.  :P

[TedWalther]

The version numbers keep changing.  I've been thinking of going through all the modules, and have a library versioning in the init.lsp file.  Be nice to update library versions in one file, then all modules could reference it.

[Lutz]

The problem should be solved by the MySQL installation with a link:



libmysqlclient.so -> libmysqlclient.so.xx.0  (where  xx is the version number)



then the mysql.lsp module could refer to just libmysqlclient.so, which is always linked to the latest on that platform. This is how it works for UBUNTU Linux and OS X and generally for libraries in /usr/lib including on OpenBSD. Perhaps somebody can find out what the standard path prefix is for MySQL on OpenBSD (and also Fedora). Then that can be added to the module together with the generic libmysqlclient.so name.