[Ipopt-tickets] [Ipopt] #215: unable to build IPOPT with MinGW-w64 x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb compiler
Ipopt
coin-trac at coin-or.org
Tue Sep 3 04:57:27 EDT 2013
#215: unable to build IPOPT with MinGW-w64
x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb compiler
---------------------+----------------------
Reporter: jpye | Owner: stefan
Type: defect | Status: assigned
Priority: normal | Component: Ipopt
Version: 3.11 | Severity: normal
Resolution: | Keywords:
---------------------+----------------------
Comment (by kelman):
I've been building the Matlab interface (mex file, equivalent to a shared
library) with static linking. And it looks like the AMPL executable and
all the test executables from these builds are also statically linked to
the GNU libs.
Ah yes, I remember TDM-GCC causing an error with -static-libstdc++. TDM-
GCC is actually set up to make that the default behavior at least with
C++, so erroring is strange IMO. A few people have complained about it...
http://sourceforge.net/p/tdm-gcc/bugs/140/
I've never needed --host or --build.
Where you need to put the flags depends on how you're interfacing to
Ipopt. Are you making an executable or shared library that statically
links to Ipopt? How does the Makefile / build system of your executable or
library work? The dependence on the GNU libraries comes from that linking
operation, probably not anything in Ipopt's build.
--
Ticket URL: <https://projects.coin-or.org/Ipopt/ticket/215#comment:11>
Ipopt <http://projects.coin-or.org/Ipopt>
Interior-point optimizer for nonlinear programs.
More information about the Ipopt-tickets
mailing list