On Wed, Sep 07, 2011 at 11:39:28AM -0500, Bob Tracy wrote: > No idea how it got missed, but simple "hello world" C programs wouldn't > compile due to a missing "libgcc_s.so --> libgcc_s.so.1" symlink. If > "ldconfig" is responsible for creating that symlink, then "ldconfig" is > broken. "libc-bin" on my system is version 2.11.2-13. I'm guessing > some kind of multi-arch transition issue.
Well on x86_64 I certainly see a number of them: gcc-4.4-multilib: /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.4/32/libgcc_s.so gcc-4.6: /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/libgcc_s.so gcc-4.4: /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.4/libgcc_s.so gcc-4.6-multilib: /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/32/libgcc_s.so gcc-4.5: /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5/libgcc_s.so Is the -multilib responsible perhaps? Not sure. I could certainly believe it could be multi-arch related. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110907173708.gj15...@caffeine.csclub.uwaterloo.ca
