Dan Nicholson wrote these words on 01/21/06 10:00 CST:
> What about just saying "If you have the system installed NSS/NSPR,
> perform this sed" and hardcode them to /usr/lib and /usr/include?
That's all I know to do right now. And I'm not a great fan of this
as Firefox/Thunderbird/Mozilla are packages that many folks will
put somewhere other than /usr. So we'd have to "if you're installing
into yada..yada..yada".
> I
> just did this sed on the thunderbird mozilla-{nss,nspr}.pc.in files.
>
> sed -i.orig \
> -e 's|libdir=.*|libdir=/usr/lib|' \
> -e 's|includedir=.*|includedir=/usr/include|' \
> build/unix/mozilla-{nss,nspr}.pc.in
Well, I found that the following sed on the *installed* files
works nicely. And it is so easy. Of course, still need "if you're
installing into yada..yada..yada"
sed -i 's|/firefox-1.5||' /usr/lib/pkgconfig/mozilla-ns*.pc
Anyway, though, how do we know that Firefox/Thunderbird won't crap
out if it doesn't find the variables to substitute for, if we
hard-code the source .in files? . I get sort of tired of testing
over and over and over. Care to try for me?
> One other thought. Since in the patch you've added
> /usr/lib/pkgconfig/nss.pc, etc., then maybe we should be suppressing
> the installation of firefox-nss.pc and thunderbird-nss.pc. Of course,
> that could break packages that don't know about nss.pc. What are your
> thoughts, Randy?
I think exactly as you do. That it could break packages that may
explicitly look for the Firefox/Thunderbird ns*.pc files.
I just thought there might be something I could do to the sources
and stick it in the existing 'system_nss' patch, without hard
coding a path.
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
10:02:01 up 118 days, 19:26, 3 users, load average: 0.84, 0.30, 0.17
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
