Configure fails. It refuses to build against Seamonkey. Yelp's error message is similar. stratos ~ # USE="-firefox" emerge -1 epiphany Calculating dependencies... done! >>> Emerging (1 of 1) www-client/epiphany-2.15.91 to / [snip] checking which gecko to use... seamonkey checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... yes checking whether we have a gecko debug build... no checking for gecko version... 1.8 configure: error: "mozilla" flavoured geckos aren't tasty enough! !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/epiphany-2.15.91/work/epiphany-2.15.91/config.log !!! ERROR: www-client/epiphany-2.15.91 failed.
It looks like epiphany 2.15 won't work with seamonkey (or mozilla) at all, but only with xulrunner or firefox. We're evaluating our options at this point. First option is that someone is going to try to patch it to work. If that fails, we may have to drop seamonkey support alltogether.
Some packages like DevHelp and Liferea have some initialization issues when built against Seamonkey, but do not show these issues when built against firefox. If upstream doesn't want to support Seamonkey, it'd silly for Gentoo to do it. We wouldn't be doing anyone a favor. I can't find a url for it, but I read a year or two ago that mozilla was no longer the official development product (read: no longer the official gecko) and that all efforts were to be focused on Firefox, and later on XulRunner. Maybe we should CC the mozilla herd to get their input on this? Dropping the seamonkey use flag portage wise, or just for gnome, and so on...
The problem with dropping seamonkey support is that there are still arches that don't have working firefox. The best solution would be to get working firefox on all arches. If that's not possible, we probably need to support seamonkey.
Hi guys. I can't emerge yelp - it fails in the configure stage: checking whether we have a gtk 2 gecko build... configure: error: This program needs a gtk 2 gecko build I've got seamonkey installed, not firefox. Got no such problem on my previous laptop where I didn't have firefox as well (probably an earlier ebuild of yelp).
Created attachment 100874 [details] config.log
Gnome 2.16 no longer builds against Seamonkey because Gnome devs decided to not support it. If yelp isn't pulling mozilla-firefox, either you need to emerge --sync or please report it here as it may be a bug. Thanks
i got this on live.gnome.org Mozilla/Seamonkey Seamonkey trunk * NOTE: Seamonkey trunk cannot be used anymore to build epiphany, as of 2006-01. http://live.gnome.org/Epiphany/MozillaPatches but if we look at the configure options of the 2.16 tarball we'll find --with-gecko[=mozilla|firefox|seamonkey|xulrunner] Which gecko engine to use (autodetected by default) i can't help more since i don't have seamonkey atm.
gnome-extra/yelp is Bug 155231 now, changing summary accordingly.
(In reply to comment #4) > Hi guys. I can't emerge yelp - it fails in the configure stage: > checking whether we have a gtk 2 gecko build... configure: error: This program > needs a gtk 2 gecko build > I've got seamonkey installed, not firefox. Got no such problem on my previous > laptop where I didn't have firefox as well (probably an earlier ebuild of > yelp). > This also happens with Mozilla Firefox 3.0 Alpha 1. Exact same error message in Yelp aswell as the following for Epiphany: checking which gecko to use... firefox checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... configure: error: This program needs a gtk 2 gecko build !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/epiphany-2.16.2/work/epiphany-2.16.2/config.log
Created attachment 107832 [details] Config.log with Firefox 3.0 Alpha 1
Yeah. Mozilla changed how they build gecko, and the detection used by gnome apps now fails. You won't be able to use firefox 3.0 alphas until gnome get's fixed (and maybe never with 2.16.x gnome...)
as said before, upstream stopped supporting seamonkey since 2.16. 2.18 has support for firefox and xulrunner. closing
