Selfupdate suddenly broken. about haxelib HOT 14 CLOSED

Seems to be an error message that is thrown during "selfupdate", but the update actually does work. On linux there is a similar error at a similar place, but it says:

/usr/bin/haxelib: 3: /usr/bin/haxelib: Syntax error: Unterminated quoted string

It would be nice to figure out what causes this and fix it. But the update appears to still work. Justin does have a separate problem, which we're trying to diagnose on IRC at the moment, and may need a separate issue :)

from haxelib.

Fresh build of haxe and after selfupdate and then after installing one haxelib on trying selfupdate again I get the error.

haxelib selfupdate
haxelib is up to date
/usr/bin/haxelib: line 2: 35819 Bus error haxe -cp "/usr/lib/haxe/lib/hxcpp/3,0,2/hxcpp/haxelib_client/3,0,0-rc,7/" -D haxelib_client --run tools.haxelib.Main $@

from haxelib.

Anybody have an idea what a "Bus error" might be? Could be this: http://stackoverflow.com/questions/212466/what-is-a-bus-error

That would be a serious error, and I don't think this is really caused by us.

AFAIK the macro interpreter still uses some stuff from neko. Maybe the error is cause there? IIRC the process API is part of that stuff, so the invocation of haxelib to get the class path of the new sources might be causing the issue.

Can you try this with a working version of haxelib?

from haxelib.

There were some linux 32-bit errors recently could it be related?
Is there a particular version of gcc that Neko should be compiled
with, I got the impression that it maybe sensitive in this respect
based on listening to some IRC discussions.

On 9 Jun 2013, at 12:46, Juraj Kirchheim wrote:

Anybody have an idea what a "Bus error" might be? Could be this: http://stackoverflow.com/questions/212466/what-is-a-bus-error

That would be a serious error, and I don't think this is really
caused by us.

AFAIK the macro interpreter still uses some stuff from neko. Maybe
the error is cause there? IIRC the process API is part of that
stuff, so the invocation of haxelib to get the class path of the new
sources might be causing the issue.

Can you try this with a working version of haxelib?

—
Reply to this email directly or view it on GitHub.

from haxelib.

I'm still not sure about the bus error, but the "/usr/bin/haxelib: 3: /usr/bin/haxelib: Syntax error: Unterminated quoted string" doesn't appear to be happening.

I upgraded from 3.0.0 to 3.0.1-rc.1 -> got the error.
From 3.0.1-rc.1 -> 3.0.1-rc.2 -> no error.

Still have to figure out if the bus error Justin is getting is haxelib related or not.

from haxelib.

Jason I made neko and haxe from scratch it seems to want to default to
a strange place??

JustinComputer:haxe justinmills$ make all haxelib
// makes everything
JustinComputer:haxe justinmills$ haxelib setup
Please enter haxelib repository path with write access
Hit enter for default (/usr/lib/haxe/lib/hxcpp/3,0,2/hxcpp)
Path :
haxelib repository is now /usr/lib/haxe/lib/hxcpp/3,0,2/hxcpp/
JustinComputer:haxe justinmills$ haxelib setup
Please enter haxelib repository path with write access
Hit enter for default (/usr/lib/haxe/lib/hxcpp/3,0,2/hxcpp)
Path : /usr/lib/haxe/lib/
haxelib repository is now /usr/lib/haxe/lib/
JustinComputer:haxe justinmills$ haxelib selfupdate
Downloading haxelib_client-3,0,0-rc,7.zip...
Download complete : 16459 bytes in 0.1s (121.8KB/s)
Created tools/haxelib/
Install tools/haxelib/Data.hx
Install tools/haxelib/Main.hx
Install tools/haxelib/Rebuild.hx
Install tools/haxelib/SemVer.hx
Install tools/haxelib/SiteApi.hx
Install haxelib.json
Current version is now 3.0.0-rc.7
Done
Error compiling haxelib client: /usr/lib/haxe/std/haxe/Json.hx:101:
characters 10-24 : Invalid package : std should be
std/Type.hx:32: characters 1-30 : Invalid package : std should be

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

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

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

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

JustinComputer:haxe justinmills$

On 12 Jun 2013, at 18:04, jasononeil wrote:

I'm still not sure about the bus error, but the "/usr/bin/haxelib:
3: /usr/bin/haxelib: Syntax error: Unterminated quoted string"
doesn't appear to be happening.

I upgraded from 3.0.0 to 3.0.1-rc.1 -> got the error.
From 3.0.1-rc.1 -> 3.0.1-rc.2 -> no error.

Still have to figure out if the bus error Justin is getting is
haxelib related or not.

—
Reply to this email directly or view it on GitHub.

from haxelib.

I'm getting the same errors on Linux 64-bit:

/usr/lib/haxe/std/haxe/Json.hx:101: characters 10-24 : 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>

from haxelib.

@TopHattedCoder: That looks like your classpath for the std library has moved up one directory. Any clue why that might happen? Maybe the problem occurs when you run selfupdate from a folder that contains the std lib and haxe uses the cwd as classpaths, thus ending up confused about packages. Can you try it from another folder?

from haxelib.

I got this error yesterday when I was trying to run haxelib just after
installing Haxe from source.

My current working directory was still inside the cloned Haxe repo, so
there was a folder called "std" in my current directory, containing the
standard library.

Is that the case for you?

If what I said doesn't make sense, just show the output of "pwd" and "ls"
respectively, and I'll be able to see if it's the same issue.

The solution was to change to a different directory and run haxelib again.
On 30/08/2013 12:27 AM, "Juraj Kirchheim" [email protected] wrote:

@TopHattedCoder https://github.com/TopHattedCoder: That looks like your
classpath for the std library has moved up one directory. Any clue why that
might happen? Maybe the problem occurs when you run selfupdate from a
folder that contains the std lib and haxe uses the cwd as classpaths, thus
ending up confused about packages. Can you try it from another folder?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-23502882
.

from haxelib.

That worked, thanks.

On Thu, Aug 29, 2013 at 5:26 PM, Juraj Kirchheim
[email protected]:

@TopHattedCoder https://github.com/TopHattedCoder: That looks like your
classpath for the std library has moved up one directory. Any clue why that
might happen? Maybe the problem occurs when you run selfupdate from a
folder that contains the std lib and haxe uses the cwd as classpaths, thus
ending up confused about packages. Can you try it from another folder?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-23502882
.

from haxelib.

The is not an issue with the 3.0.0 stable (at least on Windows anyway).

@Simn , is it possible that some post 3.0.0 updates changed the way Haxe handles nested classpaths?

from haxelib.

Sorry, missed the call here. I don't think we changed anything related to nested class paths since 3.0.0.

from haxelib.

@jasononeil Do we need to do something about this, or has it been resolved in the mean time?

from haxelib.

I don't understand the original "bus error" - if @Justinfront is still having the problem please re-open.

The Invalid package : std should be <empty> seems to be caused when trying to run haxelib (or any haxe compilation for that matter) from the Haxe source code repo. Just "cd" to a different directory and you will be fine.

If people can demonstrate the issue in any different context, please open a new issue.

from haxelib.