Need help with weird builderror

Hans de Goede j.w.r.degoede at hhs.nl
Fri Jul 27 22:46:24 UTC 2007


Hi all,

Does anyone have any hints for this error? :
http://koji.fedoraproject.org/koji/getfile?taskID=80031&name=build.log

And then specifically:
/bin/sh ../libtool --mode=link gcc  -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic 
-Wall -g   -o libWildMidi.la -rpath /usr/lib64 -shared -lm -lc  -no-undefined 
libWildMidi_la-wildmidi_lib.lo

*** 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 but no candidates were found. (...for file magic test)

*** Warning: linker path does not have real file for library -lc.
*** 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 libc but no candidates were found. (...for file magic test)
*** 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.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.

---

I've compared the configure output with a local x86_64 build and they are 
identical, so are the libtool invocations, yet here it works and on the 
buildsys it does the above?

Regards,

Hans




More information about the Fedora-maintainers mailing list