error when run haxelib after install newest haxe

143 views
Skip to first unread message

Dhemitus

unread,
Apr 2, 2015, 5:00:29 AM4/2/15
to haxe...@googlegroups.com
hi guys,

i've got error message when i run haxelib after install the newest haxe from source like this:

/usr/lib/haxe/std/neko/_std/sys/io/FileInput.hx:60: characters 26-29 : Invalid package : std should be <empty>

std/Type.hx:32: characters 1-30 : Invalid package : std should be <empty>

std/Type.hx:33: characters 1-28 : Invalid package : std should be <empty>

std/Type.hx:64: characters 15-65 : Invalid package : std should be <empty>

std/Type.hx:94: characters 15-68 : Invalid package : std should be <empty>

std/Type.hx:159: characters 15-86 : Invalid package : std should be <empty>

/usr/lib/haxe/std/haxe/zip/Huffman.hx:36: characters 16-17 : Invalid package : std should be <empty>

std/Type.hx:32: characters 1-30 : Invalid package : std should be <empty>

std/Type.hx:33: characters 1-28 : Invalid package : std should be <empty>

std/Type.hx:64: characters 15-65 : Invalid package : std should be <empty>

std/Type.hx:94: characters 15-68 : Invalid package : std should be <empty>

std/Type.hx:159: characters 15-86 : Invalid package : std should be <empty>

Juraj Kirchheim

unread,
Apr 2, 2015, 5:12:28 AM4/2/15
to haxe...@googlegroups.com
It seems like haxelib is being run in the haxe folder, thus implicitly with `-cp /usr/lib/haxe/` which clashes with the default `-cp /usr/lib/haxe/std/` . Does it occur if you run haxelib from somewhere else?

Best,
Juraj

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

Dhemitus

unread,
Apr 2, 2015, 5:24:46 AM4/2/15
to haxe...@googlegroups.com
oh yes, my bad. it's work, thank you

Juraj Kirchheim

unread,
Apr 2, 2015, 5:29:57 AM4/2/15
to haxe...@googlegroups.com
Oh, well, "works" is probably a strong word here, as this should really not happen, but I'm glad it's not completely broken ;)
Reply all
Reply to author
Forward
0 new messages