Ok. It's really easy though it can cause build problems on some platforms. I understand why you don't include it in the default build.
However, it would be nice if GLPK "configure" has an option to build reenterant binaries. Can I help you by a patch to "configure.ac" and to other build files ? If you strongly againt such option in the mainstream GLPK, please give me an advice about the recommended place in the Web to host patches to GLPK ? I made a local patch for GLPK that I use in my Java project. I want to prepare a more portable patch and to share it with other GLPK users interested in reenterable binaries. On Sun, Jan 13, 2013 at 6:32 PM, Andrew Makhorin <[email protected]> wrote: >> There were posts about reenterable version of GLPK in this list: >> http://lists.gnu.org/archive/html/help-glpk/2012-12/msg00044.html >> >> I concluded from this post that reenterability can be achieved >> by changing a line glpent02.c:31 >> from >> static void *tls = NULL; >> to >> static TLS void *tls = NULL; >> . >> TLS is configured either empty in single thread library >> or in platform-dependednt way like "__thread" in reenterable library. >> Patch could look like here: >> http://code.google.com/p/thermocompensation/source/browse/#svn%2Ftrunk%2Fglpk_patch >> Does I missed something ? >> Will GLPK-4.48 be reenterable ? >> > > Please see > http://lists.gnu.org/archive/html/help-glpk/2010-04/msg00043.html > > > _______________________________________________ Help-glpk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-glpk
