"JavaScript exception: Error: spawn ENAMETOOLONG" during compilation

[j-mueller]

Windows 10 with GHCJS installed as per the QuickStart instructions (https://github.com/ghcjs/ghcjs/blob/master/README.markdown#quick-start). Node v4.0.0

cabal install ghcjs-dom --ghcjs fails with "JavaScript exception: Error: spawn ENAMETOOLONG".

Build log here: https://gist.github.com/j-mueller/217c26434e91a812ec6e

[LukaHorvat]

Same issue here. Can't build project with a ghcjs-dom dependency. This time with stack.

[karshan]

This is probably because the command trying to be executed is too long because of the commandline arguments. On windows commandline arguments must be less than 2047 characters.

C:\Users\User\AppData\Roaming\cabal\bin\ghcjs.exe --make -fbuilding-cabal-package -O -outputdir ....... jsbits/xhr.js

[mgsloan]

Could be the commandline length, but "ENAMETOOLONG" sounds more like the windows MAX_PATH restriction. ghcjs-dom has rather long module names, and they end up in the filepath.

[mantkiew]

Was just trying to build reflex-dom-stack-demo, which depends on ghcjs-dom. Same error on Win 10.

[hherman1]

Same error here, windows 10, even trying to build in C:
Any tips from those who've been through this already would be great!

[dktr0]

Has anyone got any tips for resolving this?

[cartazio]

If it's Windows file system and Haskell modules having really long names...
Make the name shorter :)

On Wednesday, June 15, 2016, d0kt0r zer0 [email protected] wrote:

Has anyone got any tips for resolving this?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#19 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAAQwr-p_Lq1NzRn7zMHKAkyUwNaD8MMks5qMGzGgaJpZM4F-4h9
.

[dktr0]

Can't really tell if you're joking... anyway, changing the name of the many hundreds of ghcjs-dom modules and then changing the names in all the downstream packages that require them is hardly feasible. I don't believe it's the windows file system that is at fault - looks maybe more like something to do with the size of the invocation of ghcjs when building ghcjs-dom?

[cartazio]

Windows paths have a 250 char limit last I heard. Find the long name /
module that's triggering the issue.

The gl / OpenGL libs had to shorten their module names / hierarchy to work
on Windows :)

On Wednesday, June 15, 2016, d0kt0r zer0 [email protected] wrote:

Can't really tell if you're joking... anyway, changing the name of the
many hundreds of ghcjs-dom modules and then changing the names in all the
downstream packages that require them is hardly feasible. I don't believe
it's the windows file system that is at fault - looks maybe more like
something to do with the size of the invocation of ghcjs when building
ghcjs-dom?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#19 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAAQwhTiDUdrZ63HXjEwvluRGrECjvCTks5qMIDagaJpZM4F-4h9
.

[clinuxrulz]

I've read Window's max path limit has been fixed in "Windows 10 Build 14352." Upgrading windows might be the fix.

See: http://winaero.com/blog/how-to-enable-ntfs-long-paths-in-windows-10/

[clinuxrulz]

Tried the windows update, with no success. So I don't believe it to be the max character limit on the windows paths. But rather the total number characters used in the command line parameters when spawning some process becoming too many for windows to handle. (that 2047 characters that @karshan mentioned)

Here we go: VirtualBox + Linux ... sigh

[clinuxrulz]

A solution for Windows (untested at the moment):

• Install Download GNU ARM Eclipse Windows Build Tools ( http://gnuarmeclipse.github.io/blog/2015/07/15/windows-build-tools-v2.6-20150715-released/ )
• Navigate to C:\Program Files\GNU ARM Eclipse\Build Tools\2.6-201507152002\bin and run "sh"
• Then use your "stack" from the "sh". This Eclipse "sh" works around the 2047 character limit when invoking a process from the command line.

Edit: Same error in "sh", Windows build tools do not solve the problem.