Re: Firefox build problem: GetVisibility__C7nsIView undefined (Linux/PPC)

Dan Nicholson wrote:
>Steve Summit wrote:
>> I just built Firefox 1.0.7 for PPC/Linux, and the build was
>> successful, but when I try to start it up, I get:
>>       /usr/local/lib/firefox-1.0.7/firefox-bin: error while loading shared libraries:
>>       /usr/local/lib/firefox-1.0.7/components/libdocshell.so: undefined symbol: GetVisibility__C7nsIView
>
>That's pretty odd.

That's what I thought!

>> The only thing I did differently this time, I think, was to
>> add "ac_add_options --disable-tests" to my .mozconfig file.
>
> I doubt --disable-tests is the culprit unless it just happens to
> trigger a bug in the build system.

I doubt it, too.

> Are you building with debugging?

I didn't think so, although this version seems to pretty verbose
when starting up (at least, up to the point that it fails).

> Could you post your mozconfig file?

Sure.  Nothing extraordinary:

	. $topsrcdir/browser/config/mozconfig
	mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/fb-opt-dynamic
	ac_add_options --disable-tests

>> Any suggestions?
>
> Sorry, wish I did.

Thanks.

If anybody could even explain what the mechanism for loading
all the auxiliary .so libraries is, that might help me to track
the problem down.  firefox-bin doesn't seem to be explicitly
linked against any of them, only "gmodule" and "glib".  Neither
LD_LIBRARY_PATH nor any of the other environment variables seem
to be set to point into /usr/local/lib/firefox-1.0.7 or its
subdirectories.  Yet both libdocshell.so and libgklayout.so do
get loaded (out of the components subdirectory), along with many
others, and I can't figure out what mechanism or implicit
dependency it is that causes them to be loaded, which makes it
tough to track down why they're being loaded in the wrong order.

My problem probably is related to the way I built the thing,
though.  The first time I tried building Firefox 1.0.something,
I did "configure" and then "make" (assuming Firefox was like any
other package), and it failed utterly; that was before I had
learned about .mozconfig and "-f client.mk".  The second time
I tried building Firefox 1.0.something, after reading the
directions, it worked perfectly.  Unfortunately, I don't remember
exactly what I did that time, except that I'm pretty sure it was
different than what I'm trying now.  If only I had my exact
.mozconfig file and "make" invocation line from that second time,
it might be working for me now.