Running frysk within an interpreter using JNI

[Andrew Cagney <cagney at redhat dot com>]

FYI,

I've committed a prototype set of JNI bindings sufficient to run frysk's 
testsuite and, to a limited degree, run frysk utilities using an 
interpreted environment.  So far I've got frysk-sys down to 10 failures 
(and elfutils up for two bugs :-).

Once we've nailed down the remaining problems we'll be able to switch to 
these new bindings (we can also continue to compile natively) and flush 
the CNI code.  In addition, we'll be able to switch to using SOLIBS and 
greatly reduce our executable foot print.  However, in the intervening 
period we'll need to maintain both code bases.  This shouldn't be hard 
though, by using JNIXX (a JNI binding generator), I've been able 
minimise the differences so that the new bindings look and behave 
similar to CNI.

For the curious, and to make testing easier, I've also added two scripts 
to the build tree:

Runner: a hack to make invoking an interpreter easier vis:
   $ ./Runner frysk.bindir.fhpd
   vm loaded
   (fhpd) load /bin/ls
   [0.0] Loaded executable file: /bin/ls
   (fhpd)

JniRunner: JNI equivalent to TestRunner, for running the testsuite in tree:
   $ ./JniRunner frysk.testbed.TestForkFactory
   vm loaded
   Running testDetachedDaemon(frysk.testbed.TestForkFactory) ...PASS
   Running testAttachedDaemon(frysk.testbed.TestForkFactory) ...PASS
   Time: 0.45
   OK (2 tests)

Andrew