Re: Packaging a shared library with non-PIC assembly
On Mon, Jul 11, 2005 at 03:13:47PM -0400, Ryan Schultz wrote:
> On Monday 11 July 2005 02:22 pm, Frank Lichtenheld wrote:
> > On Mon, Jul 11, 2005 at 01:28:00PM -0400, Ryan Schultz wrote:
> > > I went ahead and backported all of the 0.0.4 changes into the 0.0.3 code
> > > (to keep the shipped OpenSPC code), and I'm still working out some of the
> > > kinks (I do believe that the GNU autotools hate me) but it's otherwise
> > > working.
> > >
> > > BTW, where is this bit about PIC at in the Policy? I looked through the
> > > Shared Library section but I couldn't find anything...
> >
> > It's currently only in the release team's rc policy. Both documents
> > got a bit out of sync lately... Hopefully with the new members in the
> > policy team we can fix that in the near future. As non-PIC libs cause
> > FTBFS on some arches it is almost always a RC bug anyway, policy or not.
> >
> > Gruesse,
>
> Well, libopenspc will FTBFS on all arches but i386, since the core is a bunch
> of x86 ASM written by hand, so I've set it to Architecture: i386 in
> debian/control. Is this the right thing to do? If I do this, can I safely
> override the PIC lintian error?
You need to make sure the package is listed in
"packages-arch-specific":
http://www.buildd.net/buildd/Packages-arch-specific
Justin
Reply to: