Compilation problems after FC6 to FC7 upgrade.
 

I have upgraded from FC6 to 7 on an X86_64 architecture and had relatively few problems. However when I try to build software from source (XINE and now SciLab) the ./configure stage fails when it tries to find certian libraries. An 'env' command shows that there is no LD_LIBRARY_PATH set as default for any of the users on the system, but setting this manually doesn't seem to help.

Apologies if this has been discussed elsewhere but I can't seem to find a relevant thread.

All help greatly appreciated.

Regards Russ.

Generally with a distro like Fedora missing libraries means you don't have the development package for that library not necessarily the library itself. The configure script is most likely using pkg-config to find and read the library's metadata file. Pkg-config isn't finding the metadata file. In any event, make sure you have the development package for the missing libraries installed.

BTW, LD_LIBRARY_PATH will have no impact on this; the environment variable that would is PKG_CONFIG_PATH.

Hmmm - PKG_CONFIG_PATH is not set for any users either. With XINE specifically it would not operate after the upgrade due to not finding libcurl.so.3 (nowhere to be found) so I tried a re-configure and rebuild to see if that would help. the make stage gives the following error:-

/usr/lib/libGL.so: could not read symbols: File in wrong format:

which I thought meant that it somehow was confusing 32 and 64 bit libraries...Both 32 and 64 bit libraries are on the system and also all the development libraries.

The Scilab build complains about not finding libtcl after having found the appropriate tcl.h file. Again the libraries and development libraries (64 bit only this time) are on the system.

As I say, hmmmmmm

/usr/lib/libGL.so should be the 32-bit library if FC7 is standards compliant. The 64-bit should be in /usr/lib64/libGL.so. PKG_CONFIG_PATH usually isn't set unless you have metadata files in non-standard locations or need to separate 32-bit and 64-bit versions of packages.

Can't read symbols because the file is in the wrong format sounds like you're trying to build a 64-bit binary against a 32-bit library. You don't really provide enough information to to say more than that.

I have now discovered that the run time linker has a problem with SELINUX. When I switch the mode to "permissive" all configuration and run time linking works perfectly. How do I ensure SELINUX does not conflict with the linker/loader?