Alon Keren wrote:
Alon, thanks for the detailed report. It helped a lot!
1. The reference in 'configure' (and in 'configure.in') to
'mozilla-nspr' should probably be changed to '$mozflavour-nspr'. It
works for me (and my firefox), but I don't know if it's valid also for
seamonkey:
--- OOo-2.0.2.orig/config_office/configure.in 2006-05-04
11:54:32.000000000 +0300
+++ OOo-2.0.2/config_office/configure.in 2006-05-04
12:03:15.000000000 +0300
@@ -2887,7 +2887,7 @@
if $PKG_CONFIG --exists nspr ; then
PKG_CHECK_MODULES( MOZ_NSPR, nspr )
else
- PKG_CHECK_MODULES( MOZ_NSPR, mozilla-nspr )
+ PKG_CHECK_MODULES( MOZ_NSPR, $moz_flavour-nspr )
fi
PKG_CHECK_MODULES( MOZ_NSS, nss, STANDALONENSS="TRUE",
STANDALONENSS="" )
> 2. The error in the build of 'libxmlsec' remains and, from what I saw,
> was not addressed by 'xmlsec1-1.2.6.patch' or its patch: 'mozilla-nss'
> and 'mozilla-nspr' are sought after, with no reference to other
> possible "mozilla-flavours"
Yes, these are valid. moz_flavour is simply replaced and the filenames
are the same for each package. I screwed up my test builds by leaving
the system installed nss/nspr in place. I'll have to use a clean system
with internal nss/nspr. It'll take a bit more time, but I will get to
it ASAP.
3. As for the issue of 'plugin/{base,unx}', I haven't reached that
point in the build again, but from the looks of the make-files, it
doesn't appear to be solved
Alon
I'm not sure if we can obtain those values from the toplevel makefile,
but we can certainly make configure scripts use a new moz_flavour and
test for all of the above in one shot as is done in the toplevel
config_office/configure. In these tests, the standalone tests must
occur before the mozilla/firefox/seamonkey ones.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
