This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
HTTP error 404 downloading node-sass 4.5.0 binding binary for FreeBSD 11 #1911
Assignees
Labels
Comments
|
I haven't built them yet. Will work on this. |
saper
changed the title
saper
changed the title
|
Just out of curiosity, can one build the .node file himself? If so, how is it possible to do that? Thanks in advance, |
|
|
|
If that's not happening for some reason |
|
@xzyfer , this is the complete log from the install command: it does not seem to be even trying to compile the module and when I run
nothing happens. |
|
Looks like an SSL issue connecting to nodes.org
…On 22 Feb. 2017 5:41 pm, "HiMyNameIsIlNano" ***@***.***> wrote:
@xzyfer <https://github.com/xzyfer> ,
this is the complete log from the install command:
> ***@***.*** install /usr/home/User/node_modules/node-sass
> node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm config set proxy http://example.com:8080
> ***@***.*** postinstall /usr/home/User/node_modules/node-sass
> node scripts/build.js
Building: /usr/local/bin/node /usr/home/User/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/bin/node',
gyp verb cli '/usr/home/User/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using ***@***.***
gyp info using ***@***.*** | freebsd | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/local/bin/python2
gyp verb check python version `/usr/local/bin/python2 -c "import platform; print(platform.python_version());"` returned: "2.7.13\n"
gyp verb get node dir no --target version specified, falling back to host node version: 7.5.0
gyp verb command install [ '7.5.0' ]
gyp verb install input version string "7.5.0"
gyp verb install installing version: 7.5.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 7.5.0
gyp verb ensuring nodedir is created /home/User/.node-gyp/7.5.0
gyp verb created nodedir /home/User/.node-gyp/7.5.0
gyp http GET https://nodejs.org/download/release/v7.5.0/node-v7.5.0-headers.tar.gz
gyp WARN install got an error, rolling back install
gyp verb command remove [ '7.5.0' ]
gyp verb remove using node-gyp dir: /home/User/.node-gyp
gyp verb remove removing target version: 7.5.0
gyp verb remove removing development files for version: 7.5.0
gyp ERR! configure error
gyp ERR! stack Error: unable to get local issuer certificate
gyp ERR! stack at TLSSocket.<anonymous> (_tls_wrap.js:1085:38)
gyp ERR! stack at emitNone (events.js:86:13)
gyp ERR! stack at TLSSocket.emit (events.js:186:7)
gyp ERR! stack at TLSSocket._finishInit (_tls_wrap.js:603:8)
gyp ERR! stack at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:433:38)
gyp ERR! System FreeBSD 11.0-STABLE
gyp ERR! command "/usr/local/bin/node" "/usr/home/User/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /usr/home/User/node_modules/node-sass
gyp ERR! node -v v7.5.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN enoent ENOENT: no such file or directory, open '/usr/home/User/package.json'
npm WARN User No description
npm WARN User No repository field.
npm WARN User No README data
npm WARN User No license field.
npm ERR! FreeBSD 11.0-STABLE
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "node-sass"
npm ERR! node v7.5.0
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! ***@***.*** postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ***@***.*** postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /usr/home/User/npm-debug.log
it does not seem to be even trying to compile the module and when I run
npm rebuild node-nass
nothing happens.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1911 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWE0Elv7yLA0D5mac8v0uKfTxJTyoks5re9iWgaJpZM4MHaO2>
.
|
|
if you try to copy and paste the URL used to download tbe .node module for BSD you will see it does not exist (404). This does not seem to be an SSL issue, rather the file is missing. |
|
There are two issues. The binary does not exist so you get a 404. When you try to build it locally npm needs to download the headers for Node from nodejs.org. This is failing due an SSL error. |
|
I see. So in principle if I downalod the gz file from https://nodejs.org/download/release/v7.5.0/ on to my machine, I should be able to build the module myself. If this is the case, in which folder is this to be downloaded/moved? Maybe /home/User/.node-gyp? |
|
I don't know the exact details. You'll need to check the node-gyp docs. I believe there is a flag to tell node-gyp where the headers are. |
|
I think I am going to read a bit of documentation and try to get it working while I am waiting for the binary file to be delivered. I think I also tried the |
|
Have a look at my ports on https://github.com/saper/ports-exp Fortunately FreeBSD node port installs include files in /use/local/include/node so the biggest part to get it working is adding --nodedir path to node-gyp (I am writing this from memory) |
|
so your suggestion is, instead of installing node-sass with npm, doing it via the ports tree?
The path to the node-gyp should be the place containing the downloaded header tarball or should this contain something else? |
|
It does not matter if you are using a port or when you are building by hand. |
|
I tried a to install node-sass using the library: does not seem to exist. --Edit: libuv seem to be installed on my machine and searching for uv.h I have found some occurrences of the library. |
|
I am also getting the same 404 error when attempting to downloading the binary. Same issues on multiple machines and networks, so I guess its not a proxy issue. Is there a workaround or fix? |
|
Hi @emjaksa you can try with: npm install node-sass --nodedir=/usr/local Plesse tell me if you also encouter issues with libuv. Regards, |
|
The problem may be related to an Amazon AWS S3 Outage.
|
|
There's probably some ongoing issue with AWS. Trying to install node-sass v3.13.1 linux-x64-48_binding which redirects to this link and fails. |
|
Thank you. I just heard the news about Amazon after posting. |
|
You all are awesome, thanks for the live support! Exciting! |
|
I'm also encountering this issue while npm tries to install node-sass on some Docker images, thank you for the updates! |
|
I just spent more than 2 hrs trying to figure it out why node-sass wasn't able to download D: thanks for the update! At least is not my fault :) |
|
I'm also looking for a FreeBSD version. |
|
@xzyfer , is there any news on this topic? I have been trying to search for a solution to the problem described above, that is: without any luck. Actually it is both impossible to download the *.node file from the repo and to compile it locally. I assume that if you have to provide the (I will maybe use an incorrect term) artifact, you shuould have a Freebsd box at hand and do a compile on your local machine. If this is so, could you potentially be affected by this error either? Do you have any idea how to overcome the problem? Regards, |
|
This is because node port for FreeBSD started to link to the shared, unbundled libuv. You can try fixing the Makefike in the build directory and run |
|
@saper , the only way I found to get to the makefile is htting CTRL + C, when compiling the module, I cannot find any I am everything but an expert, but I think that to build on freebsd one needs gmake. I took a look at the
Regards, |
|
@saper Let me answer that with a few other questions.
|
|
Most of the base binaries are built off of Travis-CI (Linux and OSX) and AppVeyor (Windows). The Alpine ones are built using the official NodeJS Docker image. |
|
Just for anyone who wants an immediately workable solution, the following worked for me: This uses the system install of |
|
@rterbush here is my documentation (only jail versions and node versions have changed in the meantime) https://github.com/saper/node-sass/wiki/Building-binaries-on-FreeBSD To reproduce it a FreeBSD machine running poudriere is needed, my custom ports tree overlay and one or two scrips, sell of them should be linked from there. |
|
@saper looking into the issue with travis-ci, this may be relevant. I've not yet determined if FreeBSD support has crept into travis since that issue was closed. travis-ci/travis-ci#1818 So it begs the question if the project wants to consider some other path to getting this binary built (which I am still willing to help) or perhaps preventing the attempt to download a FreeBSD binary and thus the 404 errors and just falling back to node-gyp process to build locally. |
|
@rterbush Did you check my documentation? |
|
@saper I did, but missed the part about the script you are using to copy the binary builds into the distribution area for node-sass. So that begs the question, Why are there no FreeBSD binaries if you have already worked out this process to create them? Is it just that you lack the FreeBSD machine now? |
|
@rterbush there is a simple script that copies the I had to rebuild my poudriere infrastructure on a another box and simply didn't have time to re-create all the required jails and update the ports. I have physical servers available to do that. |
|
@saper ok, so if I understand you correctly, you have the resources needed to produce the FreeBSD binaries and there is nothing I can do to help with that. |
|
@rterbush but you can try to reproduce my layout and push fixes/updates |
|
I have published bindings for node 8 for amd64 and i386 for the 4.5.3 release |
|
I have also published bindings for node 4 and node 6 for FreeBSD. Thank you for your patience! |
|
7 months to publish proper builds so people don't get a 404? Seriously? |
|
@franktopel you're more than welcome to contribute the builds. |
|
I haven't committed on doing that. Had I done so, no way would it have taken 7 months. |
|
We'd love to have you co-ordinate with @saper on contributing compatible
freebsd binaries.
…On 12 Mar. 2018 12:09 am, "Frank Topel" ***@***.***> wrote:
I haven't committed on doing that. Had I done so, no way would it have
taken 7 months.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1911 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWCSlIX6ssOR8QM1pamdM_PfmivMZks5tdSIKgaJpZM4MHaO2>
.
|
|
You refuse to get my point. When you commit to doing something (which I didn't for this purpose, and it's also beyond my field of expertise) then you do stuff in a timely fashion. 7 months for generating some binaries is way too far off from that expectation. |
|
Everyone here in the project has full freedom to do things or not to do things. Do you have a contract with node-sass maintainers that spells out the conditions of the commitment, in particular the agreed service level? |
|
Some old packages returns 404 on github. I dont know how, but using |
|
yarn add node-sass@latest |
This comment has been minimized.
This comment has been minimized.
|
The release notes for v4.7.2 has a version table that shows which Node versions ares supported. |
|
This issue was related to building bindings for Debian after a particular release. If you're coming here from search please read https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md#404-downloading-bindingnode-file |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I run
npm install node-sasson my Freebsd machine I get:The file freebsd-x64-51_binding.node does not exist. Where can one find this file?
Regards,
Daniele.
The text was updated successfully, but these errors were encountered: