> Hokey, here's another one.
>
> First off, FXRuby wouldn't compile... at all.  I got a couple of "Illegal
> number of arguments" errors, which I "fixed" by removing the offending
> arguments from the FXRuby code:
>
> diff -r FXRuby-0.99.172/src/FXRbApp.cpp FXRuby-0.99.172_/src/FXRbApp.cpp
> 100c100
> <     rb_thread_wait_for(wait);
> ---
> >     rb_thread_wait_for();
> diff -r FXRuby-0.99.172/src/FXRuby.cpp FXRuby-0.99.172_/src/FXRuby.cpp
> 138c138
> <       rb_gc_mark(value);
> ---
> >       rb_gc_mark();

Ummm, not the right "fix" (as you might have guessed). The Ruby 1.6 header
files are broken; each of those function calls (rb_thread_wait_for() and
rb_gc_mark()) were in fact passing the correct arguments. If you're using
gcc, I think you can try adding "-fpermissive" to the compiler flags
(CFLAGS) in the Makefile. I'm not sure if that's the one, but you want the
compiler flag that says "expect to see old-style C prototypes instead of
ANSI C function prototypes". Looking at the Ruby CVS repository, I see that
Matz has fixed this for Ruby 1.7 but sadly it hasn't been back-ported to
Ruby 1.6 as a bug fix.

> After I figured out the -O2 FAQ, everything compiled.  Then I figured out
the
> "Can't load library" FAQ, and got the examples to run.  However, most hang
or

.... just to refresh my memory (and to add to a real FAQ) are you talking
about making sure that the directory containing libFOX.so is in your
LD_LIBRARY_PATH? Or is this a different "Can't load library" FAQ?

> crash after they get painted.  One example does work, but I don't know
enough
> about the FOX toolkit to figure out the pattern:
>
> browser -> browser.rb:40:in `name': wrong # of arguments(0 for 1)


The browser example is definitely broken in FXRuby 0.99.172 and is fixed for
the next release.

> datatarget -> runs

Well, thank God for small favors ;)

> hello2 -> hello2.rb:50:in `run': Invalid argument - "sleep"

OK, I have absolutely no idea what this is about. I grepped through the
FXRuby source code looking for the string "sleep" to no avail. No one else
has reported this one.

> image -> image.rb:233: [BUG] Segmentation fault

Again, not sure about this one. Does it happen at startup, or as a result of
some specific action after the example's running?

> Is it me, or is it Memorex?

Mostly bad luck, but I think nothing that can't be fixed. This definitely
gives me a lot of material for a "Things That Can Go Wrong" section for the
instructions. Thanks very much for sticking it out this far.