Dan Nicholson wrote these words on 02/08/06 13:29 CST:
rm /usr/lib/pkgconfig/mozilla-ns*.pc
ln -sv nss.pc /usr/lib/pkgconfig/mozilla-nss.pc
ln -sv nspr.pc /usr/lib/pkgconfig/mozilla-nspr.pc
Okay...I'm two weeks too late to add to this thread2, but I'm doing it
anyway. :-) The _correct_ solution is for mozilla, firefox, and
thunderbird not to install the pc files at all if system nspr is
used...no symlinks either. Unfortunately, this will make difficulties
for end users. I hope that our devs and advanced users will delete the
symlinks and report back when problems surface.
For capable users: Applications looking for the
{mozilla,firefox,thunderbird}-nspr.pc file should be patched so that
they look also for nspr.pc and nss.pc, and patches then sent to the
maintainers of those broken packages. Yes, broken packages because
stand-alone nss and nspr have been available for a while now. As far as
selecting which nspr/nss to use when multiple versions are installed,
let it happen as if no change was made. IOW, --with-nspr-dir=/whatever
then the version installed in /whatever takes precedence, otherwise the
previous checks will take the first found and not continue looking for
nspr.pc after they have found {mozilla,firefox,thunderbird}-nspr.pc as
is expected. BTW, this means patching the auto files for the
maintainer, not just the configure script!
Please understand that I'm not suggesting a change to the book. I am
suggesting a change to the way that those capable of dealing with the
problems, handle the symlinks so that we can find the broken packages
and get them fixed.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
