Wrong configure options to mozilla-firefox build?

[jamesm]

Hi,

I've been trying to build Mozilla Firefox 1.0.3 with Cairo support to display SVG + Text, but I've had no luck

It appears the ebuild is correctly picking my mozsvg use flag and enabling SVG support in the firefox build but I noticed that it is calling configure with:

Code: Select all

--enable-svg-renderer-cairo

Is this correct? Last time I built this by hand it was,

Code: Select all

--enable-svg-renderer=cairo

If I open the .mozconfig file in the ebuild's temp work directory, I find this:

Code: Select all

ac_add_options --enable-svg-renderer-cairo # +mozsvg

So.. is the ebuild passing the wrong option to configure?

And the problem I have can be seen at http://users.on.net/~jamesm/wanted-svg.png and http://users.on.net/~jamesm/got-svg.png. Basically the text is being rendered at some very absurd resolution. Which is the same symptom I get when I try to display SVG text using the libart backend.

Versions of software:

Code: Select all

x11-libs/libsvg-cairo 0.15, x11-libs/cairo 0.3.0-r2, www-client/mozilla-firefox 1.0.3, x11-base/xorg-x11 6.8.2-r1

Other configure options being used:

Code: Select all

Building mozilla-firefox-1.0.3 with the following configuration
    --disable-ldap                  mozilla.org default
    --disable-mailnews              mozilla.org default
    --enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth  mozilla.org default
    --enable-crypto                 mozilla.org default
    --disable-composer              mozilla.org default
    --enable-single-profile         mozilla.org default
    --disable-profilesharing        mozilla.org default
    --enable-optimize=-O2           mozilla fallback
    --enable-old-abi-compat-wrappers  building with >=gcc-3
    --disable-installer             gentoo
    --disable-pedantic              gentoo
    --enable-crypto                 gentoo
    --with-system-jpeg              gentoo
    --with-system-png               gentoo
    --with-system-zlib              gentoo
    --without-system-nspr           gentoo
    --enable-default-toolkit=gtk2   gentoo
    --enable-ipv6                   +ipv6
    --disable-xinerama              -xinerama
    --enable-xprint                 +xprint
    --enable-freetype2              +truetype
    --enable-freetypetest           +truetype
    --disable-debug                 -debug
    --disable-tests                 -debug
    --enable-reorder                -debug
    --enable-strip                  -debug
    --enable-strip-libs             -debug
    --enable-elf-dynstr-gc          x86 optimized build
    --enable-xft                    -moznoxft
    --enable-oji                    mozilla.org default
    --enable-mathml                 mozilla.org default
    --enable-jsd                    +mozdevelop
    --enable-xpctools               +mozdevelop
    --enable-extensions=venkman     +mozdevelop
    --enable-gnomevfs               +gnome
    --enable-extensions=gnomevfs    +gnome
    --enable-svg                    +mozsvg
    --enable-svg-renderer-cairo     +mozsvg
    --with-default-mozilla-five-home=/usr/lib/MozillaFirefox  mozilla.org default
    --prefix=/usr/lib/MozillaFirefox  mozilla.org default

Any Ideas? I should also mention that the AutoFox nightly build from mozilla.org works fine with the SVG text..

[jamesm]

Looks like no one else has noticed I've just found this tidbit at http://weblogs.mozillazine.org/tor/arch ... g_b_1.html

Important SVG build configuration change

I've just checked in a build configuration change that affects how one builds with svg enabled. Previously the backend renderer always needed to be selected with --enable-svg-renderer-{gdiplus,libart,cairo}. Now the renderer defaults to reasonable values (gdiplus on win32, cairo everywhere else), and can be overridden with --enable-svg-renderer={gdiplus,libart,cairo} (note "=" instead of "-"). In most cases the only option you will need to build with native svg support is --enable-svg.

Cairo has been checked into the tree and should build when that renderer is used.

So.. who do I tell this to?

[rhill]

Bugzilla

[jamesm]

Great! My first bugzilla report filed