Re: Library packages with only static archives
Drew Hess [EMAIL PROTECTED] 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
Re: Library packages with only static archives
Thanks. Until it's fixed by the maintainer, I made my own version of the package which builds and installs libiberty.so. It's a bit of a hack, but I can submit the patch if it helps. d On Tue, 14 Dec 2004 00:41:40 +0100, Goswin von Brederlow [EMAIL PROTECTED] wrote: Drew Hess [EMAIL PROTECTED] writes: 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 What you can do meanwhile is to force users of your lib to link in libiberty.a on their own. If you have a *.la file you can add the lib there. It is not policy in debian to do so but the mechanism is there. MfG Goswin
Library packages with only static archives
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
