On Tue, May 20, 2003 at 11:59:25AM +0200, Gregor Hoffleit wrote: > * Luke Kenneth Casson Leighton <[EMAIL PROTECTED]> [030519 18:39]: > > On Mon, May 19, 2003 at 10:16:50AM -0500, Skip Montanaro wrote: > > > > > > Luke> gcc 3.3 is now the latest for unstable. > > > > > > Luke> gcc 3.3 contains a package libstdc++-5. > > > > > > Luke> python2.2 is compiled with gcc 3.2. > > > > > > Luke> installing the latest libstdc++-5, which is compiled with gcc > > > 3.3, > > > Luke> causes python2.2 to complain: > > > > > > Luke> /usr/lib/libgcc1_s.so.1 cannot find GCC_3.3 in libstdc++-5. > > > > > > Is python2.2 compiled by you from source or is it a Debian-provided > > > package? > > > > debian-provided. i've actually had to remove gcc altogether in order > > to solve the problem (!!!) > > Please report such issues to the Debian Bug Tracking System > (http://bugs.debian.org).
done that: i was just endeavouring to catch the attention of the relevant people. > I'm not able to reproduce this problem when I "apt-get install -t > unstable python2.2 gcc-3.3 g++-3.3". try adding unstable to your /etc/apt/source.list and then doing an apt-get upgrade. > On my system, python2.2 is linked > with /usr/lib/libstdc++.so.5, which is provided by the package > libstdc++5, that has been built from the gcc-3.3 source indeed. And > still python2.2 just works fine. yes but python2.2 (python2.2-5 or 6) is built and linked with gcc 3.2 not gcc 3.3. by upgrading the libstdc++.so.5 to one that was built with gcc-3.3 you get the problem that occurs on my system. > The line with /usr/lib/libgcc1_s.so.1 looks dubious. This ought to be > /lib/libgcc_s.so.1, which is provided by the libgcc1 package, which is > also derived from the gcc-3.3 source. > Can you please make sure that this is really the Debian python2.2 > binary, and that you're indeed using /usr/lib/libgcc1_s.so.1 ? yes it is the debian python2.2 binary. and /usr/lib/libgcc1_s.so.1. i appear not to have /lib in my /etc/ld.so.conf i do _not_ know why not. ... it may be because i have upgraded from debian potato on cds repeatedly over a period of at least two years? > Then, please issue an bug report including information such as the > header lines from starting python2.2, the revision numbers of the > affected packages (at least python2.2, g++-3.3, libstdc++5 and libgcc1). i have to work on this as a production system. i spent several frantic hours coming up with a procedure to recover my system back to a useable state. unfortunately i cannot risk the time it might take up on having a broken system. if all programs built with gcc-3.2 (including python2.2 and update-menus and groff and minicom and a whole boat-load of others) are replaced with programs built with gcc-3.3 then the problem i experienced goes away. l. -- -- expecting email to be received and understood is a bit like picking up the telephone and immediately dialing without checking for a dial-tone; speaking immediately without listening for either an answer or ring-tone; hanging up immediately and then expecting someone to call you (and to be able to call you). -- every day, people send out email expecting it to be received without being tampered with, read by other people, delayed or simply - without prejudice but lots of incompetence - destroyed. -- please therefore treat email more like you would a CB radio to communicate across the world (via relaying stations): ask and expect people to confirm receipt; send nothing that you don't mind everyone in the world knowing about...
