Summary: | www/node 8.5.0_1 "gyp" error during make | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Shaun Cummiskey <freebsd> |
Component: | Individual Port(s) | Assignee: | Bradley T. Hughes <bhughes> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | andreas.sommer87, w.schwarzenfeld |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Shaun Cummiskey
2017-09-26 20:24:42 UTC
I have seen reports of this error before, but I have no idea what causes it. I have not been able to reproduce it on any of my test machines, which makes it difficult to investigate and fix. I would appreciate any help in finding out what causes this. Found a lot of similar problems in the net. Seems it does not find python. Try replace USES= python:2,build with USES= python:2.7,build Btw /!\ node8-8.9.3: Makefile warnings, please consider fixing /!\ USES=python:2 is deprecated, use USES=python:2.7 Another user sent me an email with the following: "I was finally able to build node version 9.4.0 on FreeBSD 11-1. It turns out that the problem was using python build with the "DEBUG" option ON. Therefore I set the python "DEBUG" option OFF and rebuild python then I was able to build node successfully. Hopefully you can reproduce the error." I have not tried to reproduce this locally yet, but it seems that there is at least a workaround. I was not able to reproduce it with 10.4 and 11.1. (In reply to Bradley T. Hughes from comment #4) I can confirm it stemming from the DEBUG option of python27. These combinations failed for me: 103amd64 + python27-2.7.12(DEBUG) + node-{6.7.0,6.8.0,6.9.1} (in a ports tree roughly dated end 2016). As the other people, there was no reasonable error and I did not dig deeper. Is this still relevant? (In reply to w.schwarzenfeld from comment #7) I can't speak to the original conditions, as the system where I was experiencing this problem has since been upgraded from FreeBSD 11.1 to 11.2, and the version of node in ports has advanced from 8.5.0 to 11.9.0. Under this environment, node builds without any errors. I'm assuming this was fixed somewhere along the way, so I'll close out the bug. |