> JPS> Really? I can only find one source package, namely neko-1.4.tar.gz, > JPS> and it does not seem to have a way to configure for different versions > JPS> of apache, or did I miss something? > > At least there are two MS Visual Studio projects - mod_neko.vcproj and > mod_neko2.vcproj - and their configuration settings are different. I > think Linux makefile chooses which version to compile depending on the > headers it finds (but maybe I'm wrong in that, Nicolas knows better I > believe).
On Windows you can combile both mod_neko.ndll and mod_neko2.ndll from the same sources but with different flags. On other systems, mod_neko is compiled for either Apache or Apache2 depending on the version of <apache.h> that is found in the include directories on your system. So if you have only one of the two installed, it should be compiled with the installed version of Apache and will always be named "mod_neko.ndll". > JPS> $ nekoc > JPS> Uncaught exception - [EMAIL PROTECTED] This is another problem. Looks like the "nekoboot" tool doesn't work correctly on your system. Usually it will takes the "neko" commandline binary, append the bytecode at this end, and modify some bytes in the executable. Look like this is not working. Could you add some printf's in the file neko/vm/main.c (execute). data_pos should be equal to the size of the "neko" binary. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
