On Fri, 2010-12-03 at 17:06 -0600, Mario Limonciello wrote: > Jamie: > > I was well aware of this being present but it's been that way for as > far back as I can remember for libmyth* packages. With several of > those libraries in question, the code is ffmpeg code that benefits > from the performance enhancement. I would be happy to add an override > and a note to Readme.Debian as necessary if that would suffice. > > ffmpeg actually ships with an override in place, and the same build > system is used for the mythtv contained ffmpeg: > > lintian override shlib-with-non-pic-codeshlib-with-non-pic-code > ================================================================== > > The lintian overrides for the non-pic shared libs error messages is not > really a matter of silencing lintian. The general idea is that the > override would serve as an indication that we know about the error > message and we're avoiding any bug reports or complaints by others about > the errors. > > We are aware that this override is too strict. It should only cover the > i386 architecture, as we know that the upstream build system will > produce PIC libraries where necessary. Only architectures like i386 will > be built non-PIC, mainly for performance reasons. > > -- Reinhard Tartler <[email protected]>, Mon, 27 Jul 2009 12:08:55 > +0200 > The policy states that the issue must be discussed in ubuntu-devel@ and if -fPIC is not going to be used, then it be documented in README.Debian. You are following the process here, which is good. In looking at the comments in the bug[1] and the debdiff for 2:0.24.0+fixes.20101207.d3d2640-0ubuntu1 the issue is resolved for me AFAIC. Thanks for tending to it.
> Lastly, this isn't nearly as strictly enforced with other packages, > chromium's ffmpeg based package has the same error: > > #lintian > /var/cache/apt/archives/chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu0.10.04.1_i386.deb > E: chromium-codecs-ffmpeg: shlib-with-non-pic-code > usr/lib/chromium-browser/libffmpegsumo.so Perhaps, but that doesn't mean we shouldn't be enforcing it more strictly. No -fPIC is a red flag and no supporting documentation in README.Debian leads to confusion and wasted time IMO. Since this was missed when chromium-codecs-ffmpeg was deNEWed, I have now filed a bug[2] for it. Thanks for pointing this out. [1]https://launchpad.net/bugs/684941 [2]https://launchpad.net/bugs/686638 -- Jamie Strandboge | http://www.canonical.com
signature.asc
Description: This is a digitally signed message part
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
