> > > When compiling a C++ library, d-shlibs resolves the
> > > build-dependency to the virtual package libstdc++6-dev which is
> > > provided only by the libstdc++ from gcc-3.4 source package (even if
> > > the package was actually compiled using the one from gcc-4.1).
> > >
> > > Compiling same C++ library on sarge the resolving fails, trying to
> > > build-depend on non-existing libstdc++5-dev.
> > >
> > > The attached patch fixes this for the cases of using default
> > > compiler. I suspect, however, that a proper fix also taking
> > > non-default compilers into account requires changes to the objdump
> > > analysis.
> >
> > Thanks.
> >
> > I think we have a choice.
> >
> > It's part of Build-Essential, so we should be able to ignore
> > libstdc++6-XXX-dev. For non-default compilers, we should also ignore
> > libstdc++XXX-dev and leave a note to add Build-Depends on g++-XX.
>
> Ah, yes: Build-essential.
>
> But how to resolve if it was the default compiler or not?
>
> If possible to resolve which are non-default compilers, then why not
> provide build-dependencies for them now we are at it?
They are supposed to be compatible with each other, although the two
-dev packages contain different files, the actual shared library file
is one. I don't know why they decided to split the -dev package and
leave the .so file.
Is there a compelling reason to use a non-default compiler version?
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
