Xypron, Did you notice in the output, the message, "Ommitting the extension is not allowable in dl_open." ?
That means Andrew's conjecture about the platform resolving the file extension from the base name has proven not to occur. In that case, I recommend his idea of borrowing the snippet from winehq.org which conditionally sets the name based on platform via a case statement. -Chris xypron wrote: > Hello Andrew, > > I downloaded the original glpk-4.42. > In configure.ac I removed the .so extensions. > I ran autoconf;./configure --enable-dl --enable-odbc --enable-mysql; make > > This is the result: > >> ./glpsol -m sql/transp_mysql.mod > GLPSOL: GLPK LP/MIP Solver, v4.42 > Parameter(s) specified in the command line: > -m sql/transp_mysql.mod > Reading model section from sql/transp_mysql.mod... > Reading data section from sql/transp_mysql.mod... > 71 lines were read > Reading plants... > unable to open library libmysqlclient > file not found > sql/transp_mysql.mod:17: error on opening table plants > MathProg model processing error > > Ommitting the extension is not allowable in dl_open. > > You can use the following patch: > http://old.nabble.com/file/p27613410/configure.ac.patch configure.ac.patch > > For a diff display see: > http://glpk.dyndns.org/viewvc/svn/glpk/branches/glpk-4.42-sql_null_data/configure.ac?view=diff&r1=87&r2=83&diff_format=h > > Best regards > > Xypron > > > Andrew Makhorin wrote: >> Xypron, >> >>> please, have a look at >>> http://source.winehq.org/source/configure.ac >>> Learning from this example we could use the following >>> in configure.ac: >>> case $host_os in >>> darwin*|macosx*) >>> LIBIODBC="libiodbc.dylib" >>> LIBMYSQL="libmysqlclient.dylib" >>> LIBODBC="libodbc.dylib" >>> ;; >>> *) >>> LIBIODBC="libiodbc.so" >>> LIBMYSQL="libmysqlclient.so" >>> LIBODBC="libodbc.so" >>> ;; >>> esac >> Before I will make changes in configure.ac could you please check >> that omitting filename extension, i.e. >> >> LIBIODBC="libiodbc" >> LIBMYSQL="libmysqlclient" >> LIBODBC="libodbc" >> >> works correctly? It seems to me that the system shared library >> functions should be smart enough to use a standard extension if none >> is specified. >> >> >> >> _______________________________________________ >> Help-glpk mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/help-glpk >> >> > _______________________________________________ Help-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-glpk
