Hide Forgot
Description of problem: libtool contain hardcoded "4.1.1" path to gcc libsm and we are in 4.1.2 era libtool from -devel contain: sys_lib_search_path_spec=`echo " /usr/lib/gcc/x86_64-redhat-linux/4.1.1/ /usr/lib/gcc/x86_64-redhat-linux/4.1.1/ /usr/lib/gcc/x86_64-redhat-linux/4.1.1/../../../../x86_64-redhat-linux/lib/x86_64-redhat-linux/4.1.1/ /usr/lib/gcc/x86_64-redhat-linux/4.1.1/../../../../x86_64-redhat-linux/lib/ /usr/lib/gcc/x86_64-redhat-linux/4.1.1/../../../x86_64-redhat-linux/4.1.1/ /usr/lib/gcc/x86_64-redhat-linux/4.1.1/../../../ /lib/x86_64-redhat-linux/4.1.1/ /lib/ /usr/lib/x86_64-redhat-linux/4.1.1/ /usr/lib/" | $SED -e "s@${gcc_dir}@\${gcc_dir}@g;s@${gcc_ver}@\${gcc_ver}@g"` Version-Release number of selected component (if applicable): How reproducible: try to build packages like bz#222042 ... BTW, not a libtool "expert" but it isnt possible somehow instead of hardencoded string do something like: `gcc --print-search-dirs` or similar ?
To reproduce try build http://openrisc.rdsor.ro/gdal-1.4.0-7.src.rpm from bz#222042 and see why it search for 4.1.1 path while we have 4.1.2 compiler in -devel.