#39 menu_factory errors on startup
Hi,
I've got some strange problems with fuse on Solaris 8
sparc (and Intel). I've built it with GCC 3.4.3, using
GTK 2.6.4. The build completes succesfully, but when I
attempt to run the resulting binary, I get the
following messages displaye don the console :
fuse: error: couldn't get menu item
'/File/Recording/Stop' from menu_factory
fuse: error: couldn't get menu item
'/File/Recording/Record...' from menu_factory
fuse: error: couldn't get menu item
'/File/Recording/Record from snapshot...' from menu_factory
fuse: error: couldn't get menu item
'/File/Recording/Play...' from menu_factory
fuse: error: couldn't get menu item '/File/AY
Logging/Stop' from menu_factory
And so on... The interface eventually appears, however
there are no usable menu items, and there also a lot of
pop up windows containing more "menu_factory" errors. I
can see the emulator running and can type into it, so
it appears that the core of it is OK, there just seems
to be a problem with the interface.
Any idea as to what I'm doing wrong ?
Thanks,
-Mark
Another instance of bug #2065518?
After some daily upgrade (debian) i've got this error. (with widget UI too, but there, widget.c cannot compiled...)
If you check, ui/gtk/options.[ch] and ui/gtk/menu_data.c is practically empty. (the same for ui/widget/...).
hmm.. in perl/cpp-perl.pl:
push @conditions, 1;
parse_file( $ARGV[0], 1 ); -> read config.h
parse_file( $ARGV[1] ); -> read options.dat or menu_data.dat
cpp-perl does not emitt any data so, i have to change it to:
push @conditions, 1;
parse_file( $ARGV[0], 1 );
push @conditions, 1;
parse_file( $ARGV[1] );
now options.[ch] and menu_data.c autogenerated correctly...
my perl version is: Summary of my perl5 (revision 5 version 10 subversion 0)
"Another instance of bug #2065518" - yes.. sorry (or exactly #2065518 is an another instance of this bug :)
Fixed in revision 3985 - thanks again Gergely.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).