Opened 8 years ago
Closed 6 years ago
#53799 closed defect (fixed)
nodejs7 @7.7.2 Build failure
Reported by: | ghlecl (Ghyslain Leclerc) | Owned by: | ci42 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.1 |
Keywords: | Cc: | ||
Port: | nodejs7 |
Description
Tried to update NodeJS by building it. Fails everytime.
Even after clean, clean --dist and clean --all or various combinations of those. I have also uninstalled the port and tried to reinstall it. Did not work.
There seems to be a problem at the "applying patches" step of the process where the build script seems to warn that the reinplace command does nothing. I have joined a screen shot of the messages to this report. Here is an example of the warning:
Warning: reinplace s|/usr/bin/env python|/opt/local/bin/python2.7| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs7/nodejs7/work/node-v7.7.2/tools/gyp/gyp Warning: reinplace s|/usr/bin/env python|/opt/local/bin/python2.7| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs7/nodejs7/work/node-v7.7.2/deps/npm/node_modules/node-gyp/gyp/PRESUBMIT.py
Might not be related, but thought I would mention it.
I am also joining the build log that has the failure report in it. This is not the build log of my last attempt as the last attempt was stopped by SIGKILL and never finished. I had to actually use Ctrl-C after a while even if it said it received SIGKILL, which was wierd to me.
Attachments (3)
Change History (9)
Changed 8 years ago by ghlecl (Ghyslain Leclerc)
Changed 8 years ago by ghlecl (Ghyslain Leclerc)
Attachment: | SIGKILL.png added |
---|
screen_shot_1_sigkill
comment:1 Changed 8 years ago by ghlecl (Ghyslain Leclerc)
Cc: | ghlecl added |
---|
comment:2 Changed 8 years ago by ci42
Cc: | ciserlohn@… removed |
---|---|
Owner: | set to ci42 |
Status: | new → assigned |
comment:3 Changed 8 years ago by ci42
Replying to ghlecl:
There seems to be a problem at the "applying patches" step of the process where the build script seems to warn that the reinplace command does nothing. I have joined a screen shot of the messages to this report. Here is an example of the warning:
Warning: reinplace s|/usr/bin/env python|/opt/local/bin/python2.7| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs7/nodejs7/work/node-v7.7.2/tools/gyp/gyp Warning: reinplace s|/usr/bin/env python|/opt/local/bin/python2.7| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs7/nodejs7/work/node-v7.7.2/deps/npm/node_modules/node-gyp/gyp/PRESUBMIT.pyMight not be related, but thought I would mention it.
No, they are not related.
I think this is the problem:
:info:build darwintrace: socket: Too many open files in system :info:build /bin/sh: /usr/bin/grep: Too many open files in system
Could you please try again without trace mode enabled?
comment:4 Changed 8 years ago by mf2k (Frank Schima)
Cc: | ghlecl removed |
---|
As reporter, you do not need to Cc yourself.
comment:5 Changed 8 years ago by ghlecl (Ghyslain Leclerc)
Hi.
@mf2k Thanks. Wasn't sure and did not want to miss comments and seem unresponsive.
@ci42 I just did try to reinstall without trace mode enabled and it did work. Thanks for letting me know it can be a problem. I did not think it could hurt so I just enabled it by default all the time. My mistake. I'll have to read up on what it does in a little more details.
Should I be the one to mark as resolved or something ? I guess not, but just don't want to cause any problem.
Thanks again.
comment:6 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
main log