389772 - Firefox nightlies now require pangocairo

Status: RESOLVED WONTFIX

(Firefox Build System :: General, defect)

Description

[Boris Zbarsky [:bzbarsky]]

When I try to start a trunk Firefox nightly, I get:

/tmp/firefox/firefox-bin: error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory

http://wiki.mozilla.org/ReferencePlatforms/Linux claims we need pango-1.6.0-9.  I don't see how that's compatible with the pangocairo requirement....

More importantly, we don't actually _use_ pangocairo that I know of.  Why are we linking it in?

Comment 1

[Benjamin Smedberg]

Looks like it's being picked up by MOZ_GNOMEUI_LIBS, which is generated from

`pkg-config --libs libgnomeui-2.0`

This is yet another case of pkgconfig screwing us, I think: it automatically adds all the libs from Requires: statements to the output, which is pretty clearly wrong because the client app isn't going to have any direct dependency on these libs.

That said, I don't know what to do about it.

Comment 2

[Boris Zbarsky [:bzbarsky]]

The obvious options that don't involve actually fixing anything are to increase our minimum pango version requirement or to build on machines which have the minimum pango version we support installed.

As I understand, we're planning to require a much newer Pango version for Gecko 1.9 (per the last posts I saw on the topic by mconnor), so maybe this bug is just invalid.

Comment 3

[Asko Tontti]

bz: So Gecko 1.9 won't be available for RHEL4/CentOS4? Is that wise move?

Comment 4

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

It will be, but that build will come from Red Hat/CentOS.  At this point it's not likely that there will be an "official" Linux build from Mozilla, due to various distro differences.  The official builds would come from your distro vendor.  This particular bug is discussing the nightly testing builds.

Comment 5

[Asko Tontti]

vlad: thanks for the answer. Yes, I know this bug is about nightly testing builds (which right now don't work with RHEL4 so I am using old nightly 200707110404).

I was just concerned about Mozilla moving too fast forward in dropping backward compatibility. Based on the past I doubt RedHat/CentOS will release Gecko1.9/Firefox3 for RHEL4/CentOS4 but I may be wrong... [Is there more information available somewhere on the web on the Mozilla's policy change?]

Comment 6

[Benjamin Smedberg]

The requirements for gecko 1.9 are documented here: http://wiki.mozilla.org/Linux/Runtime_Requirements and were discussed in the mozilla.dev.platform newsgroup.

Comment 7

[Karl Tomlinson (:karlt)]

Can we use -Wl,--as-needed?

http://www.gentoo.org/proj/en/qa/asneeded.xml

Comment 8

[Karl Tomlinson (:karlt)]

echo 'export LDFLAGS="-Wl,--as-needed -lpthread"' >> .mozconfig
touch configure
rm obj/**/*.so
make -f client.mk build

results in no output from

  for file in **/*.so; readelf -d $file | grep pangocairo

Doesn't save loading libpangocairo on my system though because libgtk-x11-2.0.so from gtk+-2.10.13 depends on libpangocairo, and it looks like we are going to require gtk+2.10 soon:

  http://wiki.mozilla.org/Linux/Runtime_Requirements

Comment 10

[Paul Williams]

When considering what to support, please be considerate of us wonks who work at companies which allow the only Linux option to be RHEL 4.  I don't depend on RH to build supported versions of anything remotely new: the latest FF supported by RHEL4 is FF1.5.0.2 or some such silliness.

Comment 11

[Boris Zbarsky [:bzbarsky]]

Note that at this point we not only require pangocairo due to the silly build setup, but I think actually use it.  That is, I don't think we can even compile without pangocairo.  So this bug might just be invalid now.

Paul, last I checked RedHat was considering backporting a newer pango to RHEL.

Comment 13

[Zack Weinberg (:zwol)]

I'm pretty sure this is no longer even remotely relevant.