Randy McMurchy wrote:
> If this is what we have to do to make it work, then so be it. :-)
> The instructions will look funny in the book, but that is better
> than a broken build. Cut-and-paste ability is without question
> mandatory.
I did some cross checking here. My script has:
./configure --prefix=/usr \
--with-default-mozilla-five-home=/usr/lib/firefox-1.0.4 \
--with-user-appdir=.firefox \
--with-system-zlib \
--with-system-png \
--enable-application=browser \
--enable-default-toolkit=gtk2 \
--enable-extensions=cookie,xml-rpc,xmlextras,pref,\
transformiix,universalchardet,webservices,inspector,\
gnomevfs,negotiateauth \
--enable-crypto \
--enable-xft \
--enable-xinerama \
--enable-optimize \
--enable-reorder \
--enable-strip \
--enable-cpp-rtti \
--enable-single-profile \
--disable-freetype2 \
--disable-accessibility \
--disable-debug \
--disable-tests \
--disable-logging \
--disable-pedantic \
--disable-installer \
--disable-mailnews \
--disable-ldap \
--disable-composer \
--disable-profilesharing \
--with-system-jpeg
I thought we might be able to use multiple --enable-extensions lines,
but that does not work. I also note that mozilla has
--enable-extensions=all.
A agree with Randy that we need to have cut/paste work. It looks like
the the best alternative right now is to make the commands look like the
above, however, does anyone know why we don't use --enable-extensions=all?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
