Re: Library packages with only static archives

[Drew Hess <drew.hess@gmail.com>]

There aren't any Debian policy violations that I'm aware of... but I
would like to use libiberty in my own shared library, and I can't on
debian-amd64.

I have followed up on a binutils bug that was submitted 2 years ago
re: lack of shared libiberty on other archs, but I'm hoping that
raising this issue on debian-amd64 will expedite a fix.

d



On Sun, 12 Dec 2004 23:45:15 +0100, Goswin von Brederlow
<brederlo@informatik.uni-tuebingen.de> wrote:
> Drew Hess <drew.hess@gmail.com> writes:
> 
> 
> 
> > binutils-dev only supplies a static archive for libiberty.  On AMD64,
> > this means that you can't use libiberty functions in shared libraries,
> > because libiberty.a isn't compiled with -fPIC.
> >
> > Seems to me that all library packages on AMD64 should come with shared libs.
> >
> > d
> 
> You can't ever use a non PIC library with PIC code. It seems to work
> on several archs but has sideffects and randomly fails when symbols
> move around between versions.
> 
> If a shared library needs some static code then a libiberty-pic
> package or a shared libiberty is needed.
> 
> Please do file serious bugs for anyone using libiberty.a in shared
> libs. This a serious policy violation.
> 
> MfG
>         Goswin
> 
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
>