On Thu, 17 Sep 2009, Carlos R. Mafra wrote:
> > right now, basically, almost everything is linked against every
> > dependency lib, which results in a metric sh*tload of cases such as:
> >
> > /usr/bin/wmagnify:
> > Unused direct dependencies:
> >
> > /usr/lib/libtiff.so.4
>
> Do you know if that is the case for wmaker itself?
apparently so:
$ ldd -u `which WindowMaker`
Unused direct dependencies:
/usr/lib/libXft.so.2
/usr/lib/libfontconfig.so.1
/usr/lib/libXinerama.so.1
/usr/lib/libXext.so.6
/usr/lib/libX11.so.6
/lib/libdl.so.2
it's not that it's *libtiff* specifically (or
libwhatever-else specifically), it's that makefiles (driven by the
autoconf rules, i presume) pick up "random" libs, and mark "random"
binaries to be using said "random" libs.
liberal use if "ldd -u" on the binaries (even libraries) resulting
from a compilation run should reveal them secrets.
> A few days ago I did an experiment and compiled wmaker with --disable-tiff
> but the result from running 'ldd' was still showing libtiff after that...
> As I don't know much about these libraries matter, I was left wondering
> why.
that might very well be such a case. it's quite likely that that
windowmaker can't actually use tiffs, as the code to do that is not
present, still it's linked against libtiff. and we're full of that ;)
> > this should ideally be accompanied by cleaning out the unused includes
> > from sources as well.
>
> Yeah.
(i'm just leaving this in so reading this sinks into people's
unconscious mind ;)
--
[-]
mkdir /nonexistent
--
To unsubscribe, send mail to [email protected].
