I have the 2.6.11-1.1369_FC4 kernel and have problems when trying to compile certain programs such as opengl screensavers. I receive the following when compiling certain things...
make: Entering directory `/home/zypo/download/kfiresaver3d-0.6/kfiresaver3d'
/bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wbad-function-cast -Wundef -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -fno-exceptions -fno-check-new -o kfiresaver3d -L/usr/X11R6/lib64 -L/usr/lib64/qt-3.3/lib -L/usr/lib -R /usr/lib -R /usr/lib64/qt-3.3/lib -R /usr/X11R6/lib64 particle.o main.o kfiresaverkss.o kfiresaver.o kfiresaversetup.o -lkscreensaver -lqt-mt -lpng -lz -lm -lXext -lX11 -lresolv -lSM -lICE -lpthread -lresolv
libtool: link: cannot find the library `/usr/lib/libfam.la'
make: *** [kfiresaver3d] Error 1
make: Leaving directory `/home/zypo/download/kfiresaver3d-0.6/kfiresaver3d'
make: *** [all-recursive] Error 1
make: Leaving directory `/home/zypo/download/kfiresaver3d-0.6'
make: *** [all] Error 2
I have this problem with more than one program.
after some research, I found that libfam.la wasn't in /usr/lib, but in /usr/lib64. Also, If I understand correctly, the /usr/lib64 in other 64 bit distros just point to /usr/lib and have a separate /usr/lib32 directory for 32 bit programs, but FC4 has the 32 bit libs in /usr/lib and the 64 bit ones in /usr/lib64 . Am I right?
does this have anything to do with libtool?
I have also tried things such as configuring with:
./configure LDFLAGS="-R/usr/lib64 -L/usr/lib64"
which seems to semi-work for one program and then give opengl errors, but doesn't work w/ another program and still gives the same exact error above.
Does anyone know of a quick and easy solution to my problem?