--- Mer 16/12/09, Dave Korn ha scritto: > Marco Atzeri wrote: > > Hi, > > we are moving octave to automake/libtool > > and currently on cygwin I have plenty of bogus > warning > > > > libtool: link: warning: > `/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../libhdf5.la' > seems to be moved > > libtool: link: warning: > `/usr/lib/gcc/i686-pc-cygwin/4.3..4/../../../libfontconfig.la' > seems to be moved > > libtool: link: warning: > `/usr/lib/gcc/i686-pc-cygwin/4.3.4/.../../../libexpat.la' > seems to be moved > > [cut] > > > > On the built libtool library file "liboctinterp.la" > > I found both the right and the wrong "extended" > dependency > > > > ----------------------------------------- > > > > --------------------------------------------------------- > > > > Any idea/suggestion on how to convince libtool to look > for just > > /usr/lib/libhdf5.la > > instead of > > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../libhdf5.la > > > > as this seems the origin of the bogus warning ? > > Until one of the experts shows up, I'll post my > (probably half-garbled and > incomplete mis-)understanding: it depends which of the > libtool variables you > add -l and -L options to whether they get carried over into > the dependencies > or not, but if I try to remember the exact rules I'll > probably get it wrong. > > How do your liboctinterp_la_LDADD, > liboctinterp_la_LDFLAGS and/or > liboctinterp_la_LIBS definitions look? It's probably > a matter of tweaking > what goes in which one. > > cheers, > DaveK >
Dave, I suspect the problem is here, on the fortran libs path coming as default FLIBS=' -L/usr/lib/gcc/i686-pc-cygwin/4.3.4 -L/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../.. -lm -lgfortranbegin -lgfortran -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32' there is the strange /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../.. instead of the usual /usr/lib Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
