$ ldd `which curl` libcurl.so.2 => /usr/lib/libcurl.so.2 (0x27ae1000) libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7 (0x27b06000) libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7 (0x27b35000) libdl.so.2 => /lib/libdl.so.2 (0x27c25000) libz.so.1 => /lib/libz.so.1 (0x27c28000) libc.so.6 => /lib/libc.so.6 (0x27c35000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x27ac3000) $
hmmm... doesn't look as if it depend on any ligcc-3.2 On Mon, Apr 14, 2003 at 04:52:00PM +0200, Matthias Urlichs wrote: > Hi, > > On Mon, 14 Apr 2003 13:56:48 +0000, Domenico Andreoli wrote: > > i don't really know where that gcc-3.2 is coming from. as you can see curl > > doesn't depend on it explicitly. > > > If it is built with gcc-3.2 and it needs a symbol from libgcc-3.2, then > the resulting package will depend on gcc-3.2. > > I can't think of an easy fix. The packages in unstable are supposed to move to > testing as-is, and IMHO automatically trying to re-build them in testing > when that doesn't work because of auto-generated dependencies (how do you > find those?) sort of defeats the whole idea. > > Maybe it's time to force gcc-3.2 into testing..? > > > -- > Matthias > -----[ Domenico Andreoli, aka cavok --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50