Red Hat Bugzilla – Bug 402591
ruby-gnome2 (gtkmozembed) doesn't compile with xulrunner (gecko-libs 1.9)
Last modified: 2008-12-11 22:44:28 EST
Description of problem:
I've tried to build $SUBJ against xulrunner (gecko-libs 1.9) but w/o success.
I created some minimal patch (attached below) but the package uses some function
what are not exported from the latest gecko-libs (1.9):
/* enum types */
#define GTK_TYPE_MOZ_EMBED_PROGRESS_FLAGS \
#define GTK_TYPE_MOZ_EMBED_STATUS_ENUMS \
#define GTK_TYPE_MOZ_EMBED_RELOAD_FLAGS \
#define GTK_TYPE_MOZ_EMBED_CHROME_FLAGS \
GtkType gtk_moz_embed_progress_flags_get_type (void);
GtkType gtk_moz_embed_status_enums_get_type (void);
GtkType gtk_moz_embed_reload_flags_get_type (void);
GtkType gtk_moz_embed_chrome_flags_get_type (void);
I can hardly imagine if it's a bug or feature and if we need to add them to the
latest gecko or if there's any other way.
(Anyway, there's an another api change, gtk_moz_embed_set_path is used now
instead of the old gtk_moz_embed_set_comp_path)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 271221 [details]
a minimal patch, doesn't compile yet
*** Bug 408361 has been marked as a duplicate of this bug. ***
From bug #408361, here is what I currently get on a koji rebuild:
ruby-gnome2 doesn't rebuild against the latest xulrunner in rawhide:
This is the error:
xulrunner-gtkmozembed is found.
checking for gtk+-2.0... yes
checking for xulrunner-gtkmozembed... yes
checking for G_PLATFORM_WIN32... no
checking for main() in -lgtkembedmoz... no
*** .././gtkmozembed/extconf.rb failed ***
Task list and build.log here:
You have to use the attached minimal patch. gtkembedmoz.so is no more provided
by xulrunner, link against xul.so.
Attempted to apply patch to rawhide spec, still have problems (as would probably
be expected if patch is incomplete, but reporting anyway) some of which may not
One more issue:
The newest ruby-gnome2 again doesn't build with newest xulrunner...
When will xulrunner get frozen?
Well, fixed by adding BR: gecko-devel-unstable.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here: