It happens that after install all, I can use it…
But when I reboot the computer I have to execute install-haxe.sh again.
This is because the system can’t find haxe and neko, but once reinstalled all the plugins or addons are there, already installed.
Is like the script install haxe and neko on tmp/ or left something unconfigured.
If you know some solution, Thanks!
It’s the same.
After the installation, with or without reboot, after two or three hours all the modules doesn’t work anymore, so i have to do apt-get remove haxe and apt-get install haxe.
Any idea why?
I believe the current script installs to “/usr/local/bin/haxe” and “/usr/local/bin/neko” (after using the install shell script we have on the download page)
You can check and see if these are present after reboot, I can’t see why they would disappear
What are you calling module?
What happens when you type haxe in a terminal after it stopped working?
I call module because is what haxelib tells me:
Uncaught exception - load.c(181) : Module not found : run
When I type haxe works well i think:
Haxe Compiler 3.1.3 - ©2005-2014 Haxe Foundation
Usage : haxe -main [-swf|-js|-neko|-php|-cpp|-as3] [options]
Options :
-cp : add a directory to find source files
-js : compile code to JavaScript file
-swf : compile code to Flash SWF file
-as3 : generate AS3 code into target directory
-neko : compile code to Neko Binary
-php : generate PHP code into target directory
-cpp : generate C++ code into target directory
-cs : generate C# code into target directory
-java : generate Java code into target directory
-xml : generate XML types description
-main : select startup class
-lib <library[:version]> : use a haxelib library
-D : define a conditional compilation flag
-v : turn on verbose mode
-debug : add debug information to the compiled code
-help : show extended help information
–help : show extended help information
–help-defines : print help for all compiler specific defines
–help-metas : print help for all compiler metadatas
: compile the module specified by dot-path
Oh ok, so your install still works.
What does haxelib list shows?
Are you sure you used the ppa? It should be haxe 3.2.1 in it, maybe you didn’t uninstall some other version?
Does neko test works?
I’m using the ./install-haxe.sh version and not the PPA because either versions fails, and the script version works better to me.
haxelib list tell me: Uncaught exception - load.c(181) : Module not found : list
neko test tell me:
The virtual machine is working !
Calling a function inside std library…
Test successful
Your haxelib executable is corrupted (it lost its data and became just a neko),
it’s probably getting getting stripped when you reboot,
doing haxelib selfupdate after the install (when it’s still working) should help since it changes the way haxelib is called to something that won’t be stripped.
First I need to reinstall haxe with install-haxe.sh to work.
After that, when I run haxelib selfupdate this is retrieved:
Haxelib was already up to date…
Error writing file /usr/lib/haxe/haxelib. Please ensure you have write permissions.
[file_open,/usr/lib/haxe/haxelib]
And the file permissions are this:
-rwxrwxrwx 1 gonzo gonzo 158152 abr 13 2014 haxelib
I also change the user and user group to the haxelib file to root but is the same
Oh right I forgot this is broken,
then you need to do
cd /usr/lib/haxe/
cp haxelib h
./h selfupdate
rm h
I do. But…
gonzo-HP-425 gonzo # cd /usr/lib/haxe/
gonzo-HP-425 haxe # cp haxelib h
gonzo-HP-425 haxe # ./h selfupdate
Haxelib was already up to date…
gonzo-HP-425 haxe # rm h
So. I will try how it works but i think that the problem persist 
It’s because it was already downloaded, but will reinstall anyway.
So it should be good.
I make a fresh install from the PPA.
The problem continues, after a reboot it don’t work.
Haxe shows like this:
gonzo-HP-425 bin # haxe
Haxe Compiler 3.2.1 - ©2005-2015 Haxe Foundation
Usage : haxe -main [-swf|-js|-neko|-php|-cpp|-as3] [options]
Options :
-cp <\path> : add a directory to find source files
-js <\file> : compile code to JavaScript file
-swf <\file> : compile code to Flash SWF file
-as3 <\directory> : generate AS3 code into target directory
-neko <\file> : compile code to Neko Binary
-php <\directory> : generate PHP code into target directory
-cpp <\directory> : generate C++ code into target directory
-cs <\directory> : generate C# code into target directory
-java <\directory> : generate Java code into target directory
-python <\file> : generate Python code as target file
-xml <\file> : generate XML types description
-main <\class> : select startup class
-lib <\library[:version]> : use a haxelib library
-D <\var> : define a conditional compilation flag
-v : turn on verbose mode
-debug : add debug information to the compiled code
-help : show extended help information
–help : show extended help information
–help-defines : print help for all compiler specific defines
–help-metas : print help for all compiler metadatas
: compile the module specified by dot-path
neko test show this:
gonzo-HP-425 bin # neko test
Uncaught exception - load.c(181) : Module not found : test
haxelib list print this:
gonzo-HP-425 bin # haxelib list
Uncaught exception - load.c(181) : Module not found : list
I will try to uninstall and install, and do haxelib selfupdate.
Yes, your system is braking the neko executable at startup, regardless of how they were installed.
There’s a fix for that in neko, but it’s not in a released version yet.