firefox issues on a PPC running YDL-4 [long]
Joseph E. Sacco, Ph.D.
joseph_sacco at comcast.net
Thu Feb 17 09:33:21 MST 2005
The version of firefox that gets pulled down by garnome-2.9.91.1 builds
but does *not* run on a PPC running YDL-4.0.1 [see attached log].
The version built from the 16Feb05 CVS code does run properly.
==========================================================================
Discussion:
-----------
Prior to building garnome-2.9.91, I had installed a statically linked,
binary version of firefox that I had pulled down from "The Code Factory"
http://www.thecodefactory.org/mozilla/
The Code Factory version, which was built on a PPC running Debian,
Linux kunk 2.4.27 #2 Wed Oct 27 23:43:00 CDT 2004 ppc GNU/Linux
gcc version 3.3.4 (Debian 1:3.3.4-13)
works just fine on my system, so I know a version of firefox can be
built that runs under YDL-4.0.1.
I was curious about building firefox so I downloaded, built, and
installed the current development FC3 SRPM
firefox-1.08.src.rpm
It too failed to run.
I puzzled over these failures and concluded that there could be issues
with the build configuration, the source code, or both. What to do???
Yesterday I pulled down the CVS code and built firefox-1.0+ using a
simple configuration:
. $topsrcdir/browser/config/mozconfig
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/ff-opt
ac_add_options --enable-optimize
ac_add_options --disable-debug
ac_add_options --with-pthreads
ac_add_options --disable-tests
ac_add_options --enable-xft
ac_add_options --disable-freetype2
ac_add_options --enable-xinerama
ac_add_options --enable-default-toolkit=gtk2
that builds firefox under the current YDL_4.0.1 environment. Worked like
a charm!!!
Encouraged, I switched configurations and used the one provided by
garmone-2.9.91.1, adding a "configure --prefix=/opt/garmone" flag to
pick up the latest garnome libraries and includes:
. $topsrcdir/browser/config/mozconfig
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/ff-garmone
export BUILD_OFFICIAL=1
export MOZILLA_OFFICIAL=1
mk_add_options BUILD_OFFICIAL=1
mk_add_options MOZILLA_OFFICIAL=1
ac_add_options --prefix=/opt/garmone
ac_add_options --without-system-nspr
ac_add_options --with-system-zlib
ac_add_options --with-system-png
ac_add_options --with-system-jpeg
ac_add_options --with-pthreads
ac_add_options --enable-xft
ac_add_options --enable-xinerama
ac_add_options --enable-pango
ac_add_options --enable-crypto
ac_add_options --enable-default-toolkit=gtk2
ac_add_options --enable-official-branding
ac_add_options --disable-postscript
ac_add_options --disable-xprint
ac_add_options --disable-strip
ac_add_options --disable-jsd
ac_add_options --disable-mailnews
ac_add_options --disable-installer
ac_add_options --disable-ldap
ac_add_options --disable-svg
ac_add_options --disable-pedantic
ac_add_options --disable-mathml
ac_add_options --disable-composer
ac_add_options --disable-calendar
ac_add_options --disable-activex
ac_add_options --disable-tests
ac_add_options --disable-debug
ac_add_options --disable-dtd-debug
ac_add_options --disable-freetype2
That also worked...
Postmortem:
-----------
I conclude that the problem was with the particular version of the
source code and not [necessarily] the configuration.
I am still puzzling over the myriad of configuration options, trying to
ascertain "what to leave in, what to leave out".
Still running against the wind...
-Joseph
--
joseph_sacco[at]comcast[dot]net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ff.log
Type: text/x-log
Size: 7072 bytes
Desc: not available
Url : http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/attachments/20050217/9a54ce54/ff.bin
More information about the yellowdog-general
mailing list