On Thursday 18 May 2006 21:41, Gian Paolo Mureddu wrote: > Since I have been unable to build gnash for some reason or another, I was > wondering if there were any other 64-bit multilib users using gnash.
Yes, and it compiles and runs without issue here. > By > multilib 64-bit users I mean users with 64-bit Linux systems with both > versions of any given library (i386, 32-bit and x86_64, 64-bit). I don't have 32-bit versions of all libraries, only ones that are needed for backwards compatibility (e.g., OpenOffice.org). My /usr/lib is equivalent to /usr/lib64. > g++ -shared -nostdlib > /usr/lib/gcc/x86_64-redhat-linux/4.1.0/../../../../lib64/crti.o > /usr/lib/gcc/x86_64-redhat-linux/4.1.0/crtbeginS.o .libs/plugin.o > .libs/npn_gate.o .libs/npp_gate.o .libs/np_entry.o -Wl,--rpath > -Wl,/home/gianni/Programas/gnash/gnash/backend/.libs -Wl,--rpath > -Wl,/home/gianni/Programas/gnash/gnash/server/.libs -Wl,--rpath > -Wl,/home/gianni/Programas/gnash/gnash/libgeometry/.libs -Wl,--rpath > -Wl,/home/gianni/Programas/gnash/gnash/libbase/.libs -Wl,--rpath > -Wl,/usr/local/lib -L/usr/lib -L/usr/lib64 -L/home/gianni/.mozilla/plugins > -lSDL /usr/lib64/libGL.so -lGLU It's linking the 64-bit library here.. which is what you wanted, right? > /usr/lib64/libgtkglext-x11-1.0.so/usr/lib64/libgdkglext- > x11-1.0.so -lgtk-x11-2.0 -lgdk-x11-2.0 -lpango-1.0 -lcairo -latk-1.0 - > lglib-2.0 -lxml2 /usr/lib64/libz.so -lz -ljpeg -lpng -logg > ../backend/.libs/libgnashbackend.so ../server/.libs/libgnashasobjs.so > ../server/.libs/libgnashserver.so ../libgeometry/.libs/libgnashgeo.so > ../libbase/.libs/libgnashbase.so -lSDL_mixer -lrt -lX11 -lXi -lXmu > -L/usr/lib/gcc/x86_64-redhat-linux/4.1.0 > -L/usr/lib/gcc/x86_64-redhat-linux/4.1.0/../../../../lib64 -L/lib/../lib64 > -L/usr/lib/../lib64 -lstdc++ -lm -lc -lgcc_s > /usr/lib/gcc/x86_64-redhat-linux/4.1.0/crtendS.o > /usr/lib/gcc/x86_64-redhat-linux/4.1.0/../../../../lib64/crtn.o > -Wl,-soname -Wl,libgnashplugin.so -o .libs/libgnashplugin.so > > If corrected the error in the above line So.. what's the error? > , then there is apparently a > problem for libz (-lz), and others which are again seeked for under > /usr/lib instead of /usr/lib64: > > /usr/bin/ld: skipping /usr/lib/libz.so incompatible while seeking -lz > /usr/bin/ld: skipping /usr/lib/libz.a incompatible while seeking -lz > /usr/bin/ld: skipping /usr/lib/librt.so incompatible while seeking -lrt > /usr/bin/ld: skipping /usr/lib/librt.a incompatible while seeking -lrt > /usr/bin/ld: skipping /usr/lib/libm.so incompatible while seeking -lm > /usr/bin/ld: skipping /usr/lib/libm.a incompatible while seeking -lm > /usr/bin/ld: skipping /usr/lib/libc.so incompatible while seeking -lc > /usr/bin/ld: skipping /usr/lib/libc.a incompatible while seeking -lc Try configuring with LDFLAGS=-L/usr/lib64 ./configure .. . This should force it to look through that directory first. > Anyone else having such problems? If the configure script can detect > pkg-config, wouldn't it be better to use pkg-config instead for Linux > systems to avoid all these issues? (just an idea, though) I believe we don't use pkg-config because we want to use the same code on all platforms. -- Bastiaan _______________________________________________ Gnash mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash
