I'm not sure if this is a real bug or not, but at least this is perfectly reproducible. This problem was reproduced at least on three systems (both i686 and amd64). After upgrade from gcc-4.3.2-r3 to 4.3.4 revdep-rebuild started to complain about missing libgomp.la for imagemagick and imagemagick rebuild did not solved this. A bit investigation revealed that: # cd /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/ # grep libdir *.la libgfortran.la:libdir='/usr/lib/../lib64' libgfortranbegin.la:libdir='/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4' libgomp.la:libdir='/usr/lib/../lib64' libmudflap.la:libdir='/usr/lib/../lib64' libmudflapth.la:libdir='/usr/lib/../lib64' libsupc++.la:libdir='/usr/lib/../lib64' On i686 I have libdir='/usr/lib' and again the only correct path was in libgfortranbegin.la. Subsequent rebuild of libtool and gcc fixed this issue but still it looks like this could be fixed without rebuild and in any case libdir is not consistent which looks suspicious (fix_libtool_libdir_paths should work on all .la files, isn't it?). Is this a know issue or should I try to debug it? (asking in advance since each gcc rebuild, takes quite some time). Any way thanks for your time.
*** This bug has been marked as a duplicate of bug 283761 ***
