On 10/27/06, Michael Pliskin <[EMAIL PROTECTED]> wrote:
Yes, there are two versions of mod_neko, each for different apache..
Really? I can only find one source package, namely neko-1.4.tar.gz,
and it does not seem to have a way to configure for different versions
of apache, or did I miss something?
And there were some talks in haxe/neko mailing list about that
recently I think - but I also think you're following yourself.. ;)
I am now follwing both haXe and Neko mailing lists.
But that would be nice, compiling neko each time is quite a bottleneck.
I am making a Debian package, but I have run into problems. I can
compile everything, and put it in the following places:
/usr/lib/neko/libneko.so
/usr/lib/neko/mod_neko.ndll
/usr/lib/neko/mysql.ndll
/usr/lib/neko/neko
/usr/lib/neko/nekoc
/usr/lib/neko/nekoml
/usr/lib/neko/nekotools
/usr/lib/neko/regexp.ndll
/usr/lib/neko/sqlite.ndll
/usr/lib/neko/std.ndll
/usr/lib/neko/test.n
/usr/lib/neko/zlib.ndll
And made three wrappers
/usr/bin/neko
/usr/bin/nekoc
/usr/bin/nekotools
which looks like
#!/bin/sh
LD_LIBRARY_PATH=/usr/lib/neko
export LD_LIBRARY_PATH
/usr/lib/neko/neko $*
This enables me to run
$ neko /usr/lib/neko/test.n
The virtual machine is working !
Calling a function inside std library...
Test successful
however
$ nekoc
Uncaught exception - [EMAIL PROTECTED]
So it seems nekoc cannot find the stdlib. It does not help to do:
$ NEKOPATH=/usr/lib/neko:/usr/lib/neko nekoc
Uncaught exception - [EMAIL PROTECTED]
What do you do when you install neko?
--
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)
