On Tue, Nov 25, 2008 at 08:26:35PM -0600, DJ Lucas wrote: > Ken Moffat wrote: > > > > Firefox3 had *some* discussion, but there is still a lack of any > > obvious consensus. I think I'm with dj on this one, but I need to > > find time to see if I can make the included nss in 3.0.4/1.9.0.4 use > > the system libraries such as zlib. > I may look at the system zlib a little later too, but just to reiterate > on this and save a search, my suggestion was that we should provide both > separate nspr and nss for the system. However, we should add a warning > to use the included nss on Mozilla supplied packages. I'm not sure if > this warning should be carried to other packages or not...maybe the nss > page is the proper place? > > For the editors and contributors: Any package that can use a system > installed nss library, needs verification that libcrfm is not included > (and I honestly don't know its importance, only that it is built static > only and is used in xulrunner/firefox3). If it is included, then that > package requires a rebuild if a new version of nss is installed (and > probably a warning or note in the affected package's instructions). > With as little as I have been able to gather by way of grep, the rest of > the static libs installed by nss or nspr should be able to be removed, > but I haven't tested that theory just yet so use caution. Ken, where > were you with that?
I'm in agreement. I've still got far too many .a libs in my system, but most of them are from LFS and I'm stuck with those until I next build LFS. (I'm moving the awkward cases to ".hidden" in the build after I become aware of them, so that I can temporarily make them visible if I have to, e.g. zlib for module-init-tools). I also have three of them from xulrunner that I hadn't been aware of, in sdk.lib : libembed_base_a, libembed_base_standalone.a and libmozreg_s.a - getting all the static libs under control is a long process and subject to revision each time something is upgraded in my main builds. For nspr I've got no static libs installed. For nss, there are a lot I moved to '.hidden'. For the things I build, only libcrmf had to be made visible, and I see I've managed to leave it like that - according to *my* logs, only xulrunner seems to use it. But then, not much outside mozilla is using nss or nspr in my build - epiphany, evolution-data-server, totem, totem-pl-parser, yelp seem to be the only non-moz things with -lnspr in the logs. > > As for Seamonkey and Thunderbird, they will not use the newer nss/nspr > so the included ones are the only option ATM. As for using the firefox > included nss as a system nss library...I am undecided as of yet, again, > because I haven't tried that just yet. > I've just looked at my logs from the other box where I first built firefox3, without separate nss, nspr - none of the logs apart from evolution-data-server mention nspr! That one tests for nspr and nss but doesn't find them, perhaps because they are called mozilla-nspr.pc and mozilla-nss.pc. The builds for epiphany and yelp were with webkit, perhaps that's why they didn't look for nss/nspr. Totem certainly seemed to be working (i.e. browser plugins worked). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
