From: Pierre O. <os...@ce...> - 2005-12-15 09:03:56
|
Michael Gerdau wrote: >> >>*** Warning: linker path does not have real file for library -lm. >>*** I have the capability to make that library automatically link in when >>*** you link to this library. But I can only do this if you have a >>*** shared version of the library, which you do not appear to have >>*** because I did check the linker path looking for a file starting >>*** with libm and none of the candidates passed a file format test >>*** using a file magic. Last file checked: >>/usr/local/cross-w32/lib/gcc-lib/i386-mingw32msvc/3.2/../../../../i386-mingw32msvc/lib//libm.a >>*** The inter-library dependencies that have been dropped here will be >>*** automatically added whenever a program is linked with this library >>*** or is declared to -dlopen it. > > > I'm not sure wether it is of any importance but why are there > these doubled '//' in your paths ? > It gets those from the compiler so gcc's build scripts are to blame there. > And could it be that this prevents libtool from finding your > libm.a which I presume can be found under > /usr/local/cross-w32/i386-mingw32msvc/lib/libm.a > > Just guessing. > It finds it. It just doesn't like it. libtool expects a WIN32 PE file, libm.a is a archive. That's why the "fix" of removing this check works. The problem seems to be that libtool doesn't like linking static libraries to a dynamic one. I'd say this is a bit of a misfeature so the question is how to make libtool play nice. -- Rgds Pierre Ossman Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com |