On 10/29/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
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".
OK, thanks, I will see if I can produce two mod_neko packages then,
one for 1.3 and one for 2.2.
> 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.
Ahh, indeed, I stripped the executable neko* files after the size was
fixed in the bootstrap.
But now I am having some small problems with a new version of
libapr1-dev and getting the right cflags into neko.install because it
involves running pkg-config. I will sort it out eventually...
Thanks,
--
Jens Peter Secher
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
--
Neko : One VM to run them all
(http://nekovm.org)