Re: lintian warning: shlib-with-non-pic-code
- To: Brian May <bam@debian.org>
- Cc: debian-devel@lists.debian.org
- Subject: Re: lintian warning: shlib-with-non-pic-code
- From: Olaf Meeuwissen <olaf@epkowa.co.jp>
- Date: 11 Jan 2001 15:13:25 +0900
- Message-id: <[🔎] 87k88239bu.fsf@frodo.epkowa.co.jp>
- In-reply-to: Brian May's message of "20 Dec 2000 14:51:03 +1100"
- References: <84puippen5.fsf@snoopy.apana.org.au> <20001219024554.B14617@lina.inka.de> <84ae9towui.fsf@snoopy.apana.org.au> <20001219063654.A16808@lina.inka.de> <841yv3ons7.fsf@snoopy.apana.org.au> <84snnjlpi0.fsf@snoopy.apana.org.au>
Brian May <bam@debian.org> writes:
> I have fixed the problem now.
>
> Now the shared library is linked with PIC code and the static library
> is too... While this is a libtool bug, I think this is better then the
> prior situation (of non-PIC code in both the shared libary and static
> library).
>
> lintian doesn't complain any more anyway.
Perhaps a tad late, but care to tell us _how_ you fixed it? Having the
same prob with a custom (re)rolled package myself. Doesn't seem to
wreck any havoc, but would like to get rid of the lintian message
--
Olaf Meeuwissen Epson Kowa Corporation, Research and Development
Reply to: