Dear Andrew, I had trouble running glpkmex because the matlab internal libraries were intended for GCC 4.2.0 and was using the gcc compiler version 4.3...
I manually compiled the glpkmex by using gcc instead of g++, as I figured the code was in 'c' anyway, and it now gives me this error when I try to run it: >> glpktest1 LP problem ??? Invalid MEX-file '/home/workspace/seaver/Phenom_FBA/COBRA/glpkmex/glpkcc.mexglx': /home/workspace/seaver/Phenom_FBA/COBRA/glpkmex/glpkcc.mexglx: undefined symbol: _glp_lpx_write_freemps. I'm starting to think that I'll have to download and install gcc 4.2.0, will I have to do that? S On Fri, Mar 13, 2009 at 4:02 AM, Sam Seaver <[email protected]> wrote: > You know what? it does compile, I was getting the same errors with > your patch, but they are only warnings. > > Thank you > S > > 2009/3/12 Andrew Makhorin <[email protected]>: >>> I've been trying to install glpkmex for matlab, on ubuntu. I've got >>> glpk 4.29 installed, and glpkmex 2.4. I manually fixed the errors >>> about glp_long and glp_mem_usage, commented the line about xassert and >>> I still get this error: >> >>>>> makeglpkmex >>> GLPKMEX - A Matlab interface for GLPK. Script installer. >>> Version 2.4 compatible with GLPK 4.20 (or higher) >>> (C) 2001-2007, Nicolo' Giorgetti. >> >>> Do you want to use graphic installer? Y/N [Y]: N >>> GLPK path: /usr >>> GLPK path... /usr >>> GLPK include files...OK >>> GLPK library file...OK >>> -I/usr/include glpkcc.cpp /usr/lib/libglpk.aIn function ‘char* >>> strcpy(char*, const char*)’, >>> inlined from ‘void mexFunction(int, mxArray**, int, const >>> mxArray**)’ at glpkcc.cpp:707: >>> /usr/include/bits/string3.h:106: warning: call to char* >>> __builtin___strcpy_chk(char*, const char*, unsigned int) will always >>> overflow destination buffer >>> In function ‘char* strcpy(char*, const char*)’, >>> inlined from ‘void mexFunction(int, mxArray**, int, const >>> mxArray**)’ at glpkcc.cpp:711: >>> /usr/include/bits/string3.h:106: warning: call to char* >>> __builtin___strcpy_chk(char*, const char*, unsigned int) will always >>> overflow destination buffer >> >>> Any hints? >> >> You can try using a patched version of glpkcc which conforms to recent >> glpk versions. See attachment to the following message: >> http://lists.gnu.org/archive/html/help-glpk/2009-01/msg00039.html >> >> >> > _______________________________________________ Help-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-glpk
