Opened 8 years ago

Closed 4 years ago

#106 closed defect (invalid)

[Ipopt] Using ipopt with PARDISO --- Sep 2013

Reported by: sorakid Owned by: stefan
Priority: major Component: configuration tests
Version: 0.7 Keywords: Pardiso, Ipopt


Dear All,

I used to use IPOPT (3.10.4) with MA57 on my problems and it works fine. Now I want to use IPOPT with Pardiso but the problem is I cannot compile them together.

I had read several tickets about this issue (e.g:, but it seems none can solve my problem.

From previous tickets, I understand that I need to get GotoBlas? which is not supported anymore. As an alternative, I installed OpenBlas?, which is an update version of GotoBlas?. I tried to use following commands to compile it but both failed: %../configure --with-pardiso="-L$PATHTOPARDISO/ -L$PATHTOOPENBLAS/libopenblas.a -L$PATHTOGOMP/libgomp.a"

%../configure --with-pardiso="-qsmp=omp $PATHTOPARDISO/ -L$PATHTOOPENBLAS/libopenblas.a "

The error message is: checking whether user-supplied Pardiso library "-L$PATHTOPARDISO/ -L$PATHTOOPENBLAS/libopenblas.a -L$PATHTOGOMP/libgomp.a" works... configure: error: Pardiso library -L$PATHTOPARDISO/ -L$PATHTOOPENBLAS/libopenblas.a -L$PATHTOGOMP/libgomp.a does not seem to work

I also tried to check the config.log file, but please forgive me that I cannot figure out the problem. It just shows: %configure:23370: error: /bin/bash '../../Ipopt/configure' failed for Ipopt

I also attached the log file to this ticket and hope someone can help me to compile it. I appreciate your time and help in advance. ;-)



Attachments (1)

config.log (41.8 KB) - added by sorakid 8 years ago.
the config.log file

Download all attachments as: .zip

Change History (2)

Changed 8 years ago by sorakid

the config.log file

comment:1 Changed 4 years ago by stefan

  • Resolution set to invalid
  • Status changed from new to closed

We would need the config.log file from the Ipopt subdirectory.

Also this ticket would fit better into the Ipopt bugtracking system. Please create one there if this is still an issue.

Note: See TracTickets for help on using tickets.