[ATrpms-devel] Problems with Myth Packages from Bleeding Repo
jrw3319 at gmail.com
Wed Apr 18 03:40:15 CEST 2007
> AFAIK all that ldconfig's operation can do is given by ldconfig -p. And
> if some modification to ldconfig's configuration doesn't change that,
> it is very strange that there is any effect at all.
> E.g. it is strange that ldconfig itself seems to not notice the
> changes, but mythtv and alsa do.
> Axel.Thimm at ATrpms.net
> I've been looking at this for a few hours now, trying to troubleshoot the
problem, and I'm back to thinking there may be an issue with the Mythtv
packages rather than my system being hosed in some way. According to the
man page for ldconfig, the command looks at /lib and /usr/lib implicitly, as
well as directories in the ld.so.conf file. To me, this explains why the
ldconfig -p command gives the same output regardless of whether or not my
ld.so.conf file contains /usr/lib or not. If this is the case then why does
the mythbackend process only work if I add /usr/lib to ld.so.conf?
Something doesn't make sense here. I've played around with the
ld.so.conffile and it doesn't seem to matter what I have in there,
mythbackend works when the file contains /usr/lib and doesn't when /usr/lib
is removed. I've tried adding /usr/lib to two other FC6 systems and on both
systems doing this "broke" ALSA, just as it did on my mythbackend machine.
So, I'm starting to think having /usr/lib in the ld.so.conf file is not a
good thing. Who knows what else may be broken by having this in there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the atrpms-devel