Ralf Corsepius wrote:
On Mon, 2007-12-10 at 23:00 +0100, Hans de Goede wrote:
Hi All,
I just tried to build a new version of timidity and I got this build error:
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mminimal-toc -pthread -L/usr/lib64 -o calcnewt
calcnewt.o -lasound -lm -ldl -lpthread -lm -ldl -lpthread -lX11 -lm
-ldl -lpthread -lartsc -lpthread -lgmodule-2.0 -ldl -lgthread-2.0 -lrt
-lglib-2.0 -lesd -laudiofile -lm -L/usr/lib -lao -L/usr/lib -lFLAC -lm
-lncurses -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0
-lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl
-lglib-2.0 -ldl -ljack -lpthread -lrt -L/usr/lib -lvorbis -lm
-lvorbisenc -L/usr/lib -logg -lspeex -logg
./calcnewt > newton_table.c
./calcnewt: error while loading shared libraries: /usr/lib64/libjack.so.0:
R_PPC64_ADDR32 4000110d720 for symbol `' out of range
make[2]: *** [newton_table.c] Error 127
make[2]: Leaving directory `/builddir/build/BUILD/TiMidity++-2.13.2/timidity'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/builddir/build/BUILD/TiMidity++-2.13.2'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.1710 (%build)
I would guess on a multilib screw up.
At least the library paths in the compiler call above look suspicious to
me. They mix up -L/usr/lib64 and -L/usr/lib.
Depending on where these library paths originate from (*.pc's, configure
scripts?) the origin could be anywhere (even outside of your package).
I depend the -L/usr/lib getting thrown in is ugly, but AFAIK ld will simply
ignore any non 64 bit libs when linking a 64 bit binary, so this should not be
a problem, atleast it is not on x86_64.
Regards,
Hans
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
