Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Adrian Bunk
On Mon, Jan 21, 2019 at 09:42:26AM -0800, Josh Triplett wrote: > On January 21, 2019 8:48:35 AM PST, Chris Lamb wrote: > >Hi Matthias, > > > >> [...] I think I'll enable that by default in GCC 9 for bullseye. > > > >Cool. I think that therefore asking Developers to add it manually > >via Lintian

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Chris Lamb
Hi Josh, > I think there'd still be value in catching binaries that still end up > with unused dependencies for some reason, but making --as-needed the > default will certainly reduce the incidence of such issues. Getcha. Let's therefore revisit this after it becomes the default. :) Regards,

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Josh Triplett
On January 21, 2019 8:48:35 AM PST, Chris Lamb wrote: >Hi Matthias, > >> [...] I think I'll enable that by default in GCC 9 for bullseye. > >Cool. I think that therefore asking Developers to add it manually >via Lintian would therefore not be ideal - what do you think? I think there'd still be

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Chris Lamb
Hi Matthias, > [...] I think I'll enable that by default in GCC 9 for bullseye. Cool. I think that therefore asking Developers to add it manually via Lintian would therefore not be ideal - what do you think? Best wishes, -- ,''`. : :' : Chris Lamb `. `'`

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Matthias Klose
On 21.01.19 16:37, Chris Lamb wrote: > [Adding d...@debian.org to CC] > > Josh Triplett wrote: > >>> This does not sound like a good idea to me, since fixing such warnings >>> would result in many ugly (and sometimes not upstreamable) hacks. >> >> In most cases, fixing such warnings would

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Adrian Bunk
[ Josh: The BTS does not Cc submitter or commenters, so I didn't get your email. ] On Mon, Jan 21, 2019 at 03:37:02PM +, Chris Lamb wrote: > [Adding d...@debian.org to CC] > > Josh Triplett wrote: > > > > This does not sound like a good idea to me, since fixing such warnings > > >

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Chris Lamb
[Adding d...@debian.org to CC] Josh Triplett wrote: > > This does not sound like a good idea to me, since fixing such warnings > > would result in many ugly (and sometimes not upstreamable) hacks. > > In most cases, fixing such warnings would involve either adding > --as-needed or just

Bug#919957: Please check for binaries depending on unused libraries

2019-01-21 Thread Josh Triplett
On Mon, 21 Jan 2019 08:39:27 +0200 Adrian Bunk wrote: > On Sun, Jan 20, 2019 at 03:45:35PM -0800, Josh Triplett wrote: > > I'd love to see lintian catch issues like this: > > > > $ ldd -u /sbin/badblocks > > Unused direct dependencies: > > /lib/x86_64-linux-gnu/libblkid.so.1 > > > > Lintian

Bug#919957: Please check for binaries depending on unused libraries

2019-01-20 Thread Adrian Bunk
On Sun, Jan 20, 2019 at 03:45:35PM -0800, Josh Triplett wrote: > Package: lintian > Version: 2.5.122 > Severity: normal > > I'd love to see lintian catch issues like this: > > $ ldd -u /sbin/badblocks > Unused direct dependencies: > /lib/x86_64-linux-gnu/libblkid.so.1 > > Lintian already

Bug#919957: Please check for binaries depending on unused libraries

2019-01-20 Thread Josh Triplett
Package: lintian Version: 2.5.122 Severity: normal I'd love to see lintian catch issues like this: $ ldd -u /sbin/badblocks Unused direct dependencies: /lib/x86_64-linux-gnu/libblkid.so.1 Lintian already parses binaries and libraries with objdump, so catching this seems reasonable. --