On 1/21/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> 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".
But it only affects the situation where the user has a system
installed NSS/NSPR, which most likely will be in /usr. So, all you
need to say is "If you are using the system NSS, do this sed,
replacing /usr with the prefix where it was installed." Everyone else
can pass right by because their situation will be handled
automatically.
> 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?
Because Firefox/Thunderbird/Mozilla don't depend on the pkg-config
variables. They already know these variables and fill in the .pc
files for the benefit of other apps that want to use their libraries.
It would only be broken if the change wasn't made. You can delete
those .pc files if you want. It won't affect Firefox/Thunderbird.
> 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.
OK, now I see what you mean. Unfortunately, I don't see a general fix
here. Well, if you remove them from the source tree, they won't be
installed and you have to depend on the system nss.pc files.
If you want, I could add some vars and make it generic. All you need
is to pull all the variables out of {nspr,nss}.pc if they exist and
add change mozilla-{nss,nspr}.pc to use those vars.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
