Am Mi, 2003-07-16 um 09.21 schrieb Luca Berra: > libgcc_s.so.1 really belogs to /lib go and fix your distro > L. Why that? I know, usually gcc installs it into /usr/lib, but I don't think there is anything wrong with this way of doing things. Gentoo installs some things into the gcc directory that comes with gcc and puts wrappers into /usr/bin. It's much easier to installing several compiler versions in parallel and uninstalling them afterwards without having trouble. Look at the mess on my other systems where I compiled everything by hand and I've got a chaos in /usr/lib. And the directories are listed in /etc/ld.so.conf anyway, so what's the problem? But he's right. This is strange. On my gentoo system with gcc 3.3 lvm2 doesn't get linked to libgcc.so either. Something has to be different on his system. Where's the depencency coming from? From libdevmapper.so or from the tool itself? -- Christophe Saout <christophe@saout.de> Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
