could somebody please clean this up? [root@srv-rhsoft:~]$ symlinks -r / | grep dangling | grep gcc dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libstdc++.a -> ../../../i686-redhat-linux/4.7.2/libstdc++.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libgcc_s.so -> /lib/libgcc_s.so.1 dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libmudflapth.a -> ../../../i686-redhat-linux/4.7.2/libmudflapth.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libmudflap.a -> ../../../i686-redhat-linux/4.7.2/libmudflap.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libsupc++.a -> ../../../i686-redhat-linux/4.7.2/libsupc++.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libquadmath.a -> ../../../i686-redhat-linux/4.7.2/libquadmath.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libgomp.so -> ../../../../libgomp.so.1.0.0 dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libitm.a -> ../../../i686-redhat-linux/4.7.2/libitm.a dangling: /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libstdc++.so -> ../../../../libstdc++.so.6.0.17 [root@srv-rhsoft:~]$ rpm -q --file /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libstdc++.a gcc-c++-4.7.2-8.fc18.x86_64 [root@srv-rhsoft:~]$ rpm -q --file /usr/lib/gcc/x86_64-redhat-linux/4.7.2/32/libgcc_s.so gcc-4.7.2-8.fc18.x86_64
This is intentional, so that the package supports both -m64 and -m32 compilation, if you install the 32-bit rpms things work automatically, but that the 32-bit packages aren't required.
intentionally broken? why do not only the 32bit rpms create these symlinks? yes, ifarch-constrcuts in SPEC-file exists
Why do you use a word broken? I don't see anything broken on the current state. And, the 32-bit packages shouldn't be putting symlinks into the paths they shouldn't own (x86_64 specific paths).
because the symlinks are broken? this is how a symlink pointing to nowhere is called! sorry, but i do *really* not understand why a 100% clean x86_64 setup is cluttered with symlinks pointing to nowhere somebody *could* find useable if he has 32bit packages installed i killed them multiple times because and thought they where from non-perfect dist-upgrades but after find them again i looked which package clutters my machine