Zaiwen,<br>
<br>
Thanks for the info. The problem occured because IPOPT (ipoma.f)
opened a file called OUTSDIF.d (UNIT=60) and then passed the unit
number to CSETUP subroutine of the CUTEr package. CUTEr was
compiled with Intel Fortran and IPOPT with gfortran. Apparently
they don't share open files well. There were no linking issues
and I didn't have to do steps #1 or #3. I just recompiled CUTEr
and SIFDEC with g95.<br>
<br>
Another quick piece of advise for those compiling CUTEr and SIFDEC with
g95 option: I had to make a symbolic link because they changed
the name of the compiler for the new compiler name in Fedora Core 4.<br>
<br>
ln /usr/bin/gfortran /usr/bin/g95 --symbolic<br>
<br>
<br>
-John <br><br><div><span class="gmail_quote">2006/2/2, Zaiwen Wen <<a href="mailto:zw2109@columbia.edu">zw2109@columbia.edu</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>My configuration for Ipopt is:<br><br>./configure --with-blas="-L/opt/intel/mkl721/lib/32 -lmkl_lapack<br>-lmkl_ia32 -lguide -lpthread" \<br> CXXLIBS='-L/usr/lib/gcc/i386-redhat-linux/4.0.2 -lstdc++ -lm -lgcc '
<br> F77=gfortran<br><br>My configuration for CUTEr is:<br> CUTEr.large.pc.lnx.g95<br><br><br>I have the following experience:<br><br>1. in File /Apps/CUTErInterface/CUTErInterface.f<br><br>----------------------------------------
<br>C<br>C Call IPOPT<br>C<br> IPROBLEM = IPCREATE(N, X_L, X_U, M, G_L, G_U, NELE_JAC, NELE_HESS,<br> 1 EV_F, EV_G, EV_GRAD_F, EV_JAC_G, EV_HESS)<br><br>---------------------------------------<br><br>should be:
<br><br>--------------------------------------<br><br><br> IPROBLEM = IPCREATE(N, X_L, X_U, M, G_L, G_U, NELE_JAC, NELE_HESS,<br> 1 IDX_STY, EV_F, EV_G, EV_GRAD_F, EV_JAC_G, EV_HESS)<br><br>one should also add definition:
<br> integer IDX_STY<br> parameter (IDX_STY = 1 )<br>---------------------------------------<br><br>The definition of the function "IPCREATE" is in file:<br> /Interfaces/IpStdFInterface.c<br>
<br><br>2. According to my experience, if the fortran compiler for ipopt and CUTEr<br>are different, there will be some conflictions during compilation when<br>using "sdipo\ipo".<br><br><br>3.<br><br>Since the new script "ipo" defines
<br> setenv SYSLIBS "`cat ${MYCUTER}/double/lib/ipo.liblist`",<br>it will probably cause some problems for the following lines in the<br>script "runpackage" in "CUTEr/mycuter/bin"<br><br>$LOAD $FFLAGS -o ${PAC}min
ELFUN.o GROUP.o RANGE.o $EXTER $DRIVER \<br> $SUBR $ALT_LIB_PATH -L$LIBDIR $SYSLIBS -lcuter $BLAS $LAPACK<br><br>After these two lines modifed to:<br><br>$LOAD $FFLAGS -o ${PAC}min ELFUN.o GROUP.o RANGE.o $EXTER $DRIVER \
<br> $SUBR $ALT_LIB_PATH -L$LIBDIR -lcuter $SYSLIBS<br><br>sdipo and ipo work perferctly.<br><br><br><br>Wish these information will be helpful.<br><br><br>Best Regards!<br>Zaiwen<br></blockquote></div><br>