[Coin-ipopt] Difficulities in installation on SunOS

Andreas Waechter andreasw at watson.ibm.com
Fri Aug 19 14:06:23 EDT 2005


Hi Danh,

You were correct, the Makefile for the example did not automatically
include the -xlic_lib=sunperf flag if it was detected to work.

I corrected the configure script and submitted it to COIN.  It is already
available via CVS, and will be in tomorrow's tarball.

I will also send you the corrected configure script in a separate email.

Sorry for the hassle,

Andreas

On Thu, 18 Aug 2005, Andreas Waechter wrote:

> Danh,
>
> I'm not convinced the installion was not successful.  Did you run the
> example compilation with exactly the Makefile that is produced after you
> run configure (In that case you should see the Fortran flags you
> specified for configure's FFLAGS)?
>
> The configure script tries to find out if there are precompiled versions
> of lapack and blas installed on the system.  On SUN compilers, there is
> the flag -xlic_lib=sunperf that one can specify and enables the inclusion
> of optimized BLAS and LAPACK libraries.
>
> If the configure script finished, it means that it either found these
> libraries provided by SUN, or that it checked that you obtained the source
> code.  In the first case, the automatically generated Makefile for the
> example will include whatever flag is necessary to get BLAS (like
> -xlic_lib=sunperf), and in the second case, the BLAS and LAPACK code will
> be compiled when you type make install, and the objects are included in
> the libipopt.a
>
> Since the symbols are missing despite the fact that you include -lipopt,
> your configure script must have determined that -xlic_lib=sunperf works.
> It strongly seems to me that the reason you can't link the example is that
> you don't use the right Makefile.
>
> Hope this helps
>
> Andreas
>
> On Thu, 18 Aug 2005, Nguyen An Danh wrote:
>
> > Hi Andreas,
> > It is definitely that Ipopt installation is not sucessful.
> > I checked /lapack and /blas.  Fortran files are still there but I do not seen
> > object files
> > Danh.
> >
> > On Thursday 18 August 2005 18:04, you wrote:
> > > Hi Danh,
> > >
> > > 1. It seems that BLAS and LAPACK are missing when you try to link the
> > > example?  It seems to me that you are not using the Makefile that is
> > > produced by configure for the example?  (FFLAGS for configure is '-O5
> > > -xtarget=native', but when you compile the example you have '-O
> > > -xtarget=native').  The Makefile for the example is created automatically
> > > to fit whatever configure finds out.  If you make changes to that
> > > Makefile, things might not work.  So, first try to compile the example
> > > with the Makefile that is installed by configure, and if that works, you
> > > can start making changes.
> > >
> > > 2. As for your Linux cluster compilation - check the 'config.log' file.
> > > The configure script finds the Intel compiler icc, but there seems to be a
> > > problem on your system with that compiler.  If you want to use a different
> > > compiler, specify it with CC='gcc' and F77='g77', for example.
> > >
> > > Andreas
> > >
> > > On Thu, 18 Aug 2005, Nguyen An Danh wrote:
> > > > Hi Andreas,
> > > > Are you still online?
> > > >
> > > > 1.  I have just tried
> > > > ./configure F77=mpf77 FFLAGS='-O5 -xtarget=native'
> > > > Unfortunately, it does not fix the problem. :-((
> > > >
> > > > SUNOS:sunc26:COIN/Ipopt/EXAMPLES/Fortran_example[30]$ make
> > > > mpf77 -O -xtarget=native -c -o example.o `test -f 'example.f' || echo
> > > > './'`example.f
> > > > NOTICE: Invoking /opt/SUNWspro/bin/f90 -f77 -ftrap=%none -I/opt/SUNWhpc/
> > > > include -O -xtarget=native -c -o example.o example.f
> > > > f90: Warning: -xarch=native has been explicitly specified, or implicitly
> > > > specified by a macro option, -xarch=native on this architecture implies
> > > > -xarch=v8plusb which generates code that does not run on pre UltraSPARC
> > > > III processors
> > > > example.f:
> > > >  MAIN example:
> > > >         ev_f:
> > > >         ev_g:
> > > >         ev_c:
> > > >         ev_a:
> > > >         ev_h:
> > > > bla=;\
> > > > for file in example.o; do bla="$bla `echo $file`"; done; \
> > > > mpf77 -O -xtarget=native -o example $bla -L/home/gn046ng/COIN/Ipopt/lib
> > > > -lipopt
> > > > NOTICE: Invoking /opt/SUNWspro/bin/f90 -f77 -ftrap=%none
> > > > -L/home/gn046ng/COIN/ Ipopt/lib -I/opt/SUNWhpc/include -R/opt/SUNWhpc/lib
> > > > -L/opt/SUNWhpc/lib -O -xtarget=native -o example example.o -lipopt
> > > > f90: Warning: -xarch=native has been explicitly specified, or implicitly
> > > > specified by a macro option, -xarch=native on this architecture implies
> > > > -xarch=v8plusb which generates code that does not run on pre UltraSPARC
> > > > III processors
> > > > Undefined                       first referenced
> > > >  symbol                             in file
> > > > ddot_                               /home/gn046ng/COIN/Ipopt/lib/
> > > > libipopt.a(linesearch.o)
> > > > ...
> > > > dspevx_                             /home/gn046ng/COIN/Ipopt/lib/
> > > > libipopt.a(get_pz_cg.o)
> > > > idamax_                             /home/gn046ng/COIN/Ipopt/lib/
> > > > libipopt.a(linesearch.o)
> > > > ld: fatal: Symbol referencing errors. No output written to example
> > > > *** Error code 1
> > > > make: Fatal error: Command failed for target `example'
> > > >
> > > > 2. Then I decided to test on Linux-cluster, and here is message:
> > > > LINUX:linuxoc01:/home/gn046ng/COIN/Ipopt[55]$ ./configure
> > > > checking build system type... x86_64-unknown-linux-gnu
> > > > checking for icc... icc
> > > > checking for C compiler default output file name... configure: error: C
> > > > compiler cannot create executables
> > > > See `config.log' for more details.
> > > >
> > > > In config.log it reports that :
> > > > LINUX:linuxoc01:/home/gn046ng/COIN/Ipopt[55]$ ./configure
> > > > checking build system type... x86_64-unknown-linux-gnu
> > > > checking for icc... icc
> > > > checking for C compiler default output file name... configure: error: C
> > > > compiler cannot create executables
> > > > See `config.log' for more details.
> > > >
> > > > Danh.
> > > >
> > > > _______________________________________________
> > > > Coin-ipopt mailing list
> > > > Coin-ipopt at list.coin-or.org
> > > > http://list.coin-or.org/mailman/listinfo/coin-ipopt
> >
> > _______________________________________________
> > Coin-ipopt mailing list
> > Coin-ipopt at list.coin-or.org
> > http://list.coin-or.org/mailman/listinfo/coin-ipopt
> >
>
> _______________________________________________
> Coin-ipopt mailing list
> Coin-ipopt at list.coin-or.org
> http://list.coin-or.org/mailman/listinfo/coin-ipopt
>




More information about the Coin-ipopt mailing list