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

Steve Summit wrote:
> If you have pointers to any information on what the 2.95.3
> problem specifically was, I'd be curious.

I believe that the GCC versions with this problem do not correctly emit 
inline functions and instead expect them to be in the file where the 
first (virtual?) function is.

https://bugzilla.mozilla.org/show_bug.cgi?id=213839 is essentially the 
same problem, and I believe there were a few similar bug reports too.

Hmm. I wonder if this is a binutils bug instead? You are sure that the 
compiler versions are identical?

> But anyway, after playing around with a couple of other options
> (including --enable-default-toolkit, which seemed promising,
> since it's not clear whether that's optional or required)

optional. Virtually nobody will need it. The default for this option is 
probably the best one for most users.

> without success, I finally left a static build running overnight
> last night.  And... it works!  It starts up much quicker, too,
> and it doesn't seem to be killing my machine on RAM usage,
> either. 

The RAM usage thing was only during compile. It may need a little bit 
less RAM during runtime, but probably not enough to notice.

> One last comment, in case any Firefox developers or documenters
> are listening: besides listing the known problem with gcc 2.95.3
> somewhere if that's missing,

I dunno, maybe that compiler works for some people... I know that it 
works on BeOS, for example.

> 	Selects the graphics toolkit.  This is not needed
> 	for Windows/OS2/BeOS/Photon, since these platforms
> 	automatically select the correct toolkit.  It is also
> 	not needed on Mac, unless you are building Camino...

Hm... yeah, that's misleading. Really, what is the case it that only on 
linux do you have a real choice (GTK1/Gtk2/Xlib/Qt; gtk2 is the default 
and works best). Now, lately, there's also the cairo-* possibilities, 
but those builds are really mainly for developers at the moment.

>   (This strategy was designed so that I could
> frustrate myself with incomplete information in precisely such
> cases as this one. :-) )

:-)