-
Notifications
You must be signed in to change notification settings - Fork 298
Build Fails on FreeBSD Error: incorrect header check at Zlib #282
Comments
Any idea how to fix/work around it? |
This throw er; turns out to be the fact that apm is trying to download a binary package of node to run and freebsd isn't in the list of built packages. http://nodejs.org/dist/v0.10.35/ % node ./script/download-node.js If we are building from source, maybe we can just skip this install step and use the native node. |
Closed by #360 |
This doesn't fix the issue completely for freebsd, it simply help understand better what happens (404 downloading node). In practice the zlib issue is gone but compilation still fails for freebsd, and node is already installed anyway, if node is installed why even try to download it again? If the error is 404 but node is installed apm build should proceed. |
Sorry for the spam, but I was looking at the what the ports are getting as a distfile, and it seems its "node-v0.xx.x.tar.gz", so maybe a good way to handle it would be to just check if its freebsd and download the tar.gz So basically if its "freebsd" remove "process.platform" (edit: and arch too), I could make a PR for that change if it sounds reasonable? |
Yes, this is a baby step. It keeps it from throwing an exception. I hope we can make it fall back to the native version. In the mean time, use this patch: |
Sounds ok, I'm my case I had to use ln -s instead of creating a hard link but this is a nice workaround for now. |
Yeah, mine is one big ZFS tank. I'll change that diff to use a symbolic link. This will point atom at the patched apm. |
Ok, will try that now, btw bin/apm is using the /bin/bash shebang... probably best to use "#!/usr/bin/env bash" as not all os have bash in the same place, and in freebsd its installed to /usr/local/bin so it would fail. *EDIT: same for atom.sh |
Yes, using env is good practice. but dedupe seems happy: |
events.js:72
throw er; // Unhandled 'error' event
^
Error: incorrect header check
at Zlib._binding.onerror (zlib.js:296:17)
The text was updated successfully, but these errors were encountered: