[Python-Dev] [debian build error]

Gregor Hoffleit flight@debian.org
Tue, 20 May 2003 11:59:25 +0200


* Luke Kenneth Casson Leighton <lkcl@samba-tng.org> [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).

I'm not able to reproduce this problem when I "apt-get install -t
unstable python2.2 gcc-3.3 g++-3.3". 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.

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 ?


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).


Thanks,

    Gregor