Bug 233049 - www/node10: build fails. torgue dumps core on fresh installed x386 BSD
Summary: www/node10: build fails. torgue dumps core on fresh installed x386 BSD
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: i386 Any
: --- Affects Many People
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-07 05:58 UTC by Jens Nykaer
Modified: 2019-08-13 12:04 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (bhughes)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Nykaer 2018-11-07 05:58:24 UTC
Installing using portmaster. Dependencies checks out.

touque produces a dump

Build-instructions in README file at /usr/ports/www/node10/work/node-v10.13.0/deps/v8/gypfiles have a empty URL.  Will chech scour for build-instructions elsewhere.


<SNIP>
/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPath.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/
third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPathElement.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4
/runtime/Cpp/runtime/src/tree/xpath/XPathLexer.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime
/src/tree/xpath/XPathLexerErrorListener.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tr
ee/xpath/XPathRuleAnywhereElement.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpa
th/XPathRuleElement.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPathTokenA
nywhereElement.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPathTokenElemen
t.o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPathWildcardAnywhereElement.
o /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj.host/torque/deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/xpath/XPathWildcardElement.o /usr/por
ts/www/node10/work/node-v10.13.0/out/Release/obj.host/deps/v8/gypfiles/libv8_libbase.a -lz -L/usr/local/lib -luv -lcares -lnghttp2 -lelf -L/usr/local/lib -lexecinfo
 -Wl,--end-group
  touch f83d073c12b622af305dd74b713a0eb672e0bcba.intermediate
  LD_LIBRARY_PATH=/usr/ports/www/node10/work/node-v10.13.0/out/Release/lib.host:/usr/ports/www/node10/work/node-v10.13.0/out/Release/lib.target:$LD_LIBRARY_PATH; ex
port LD_LIBRARY_PATH; cd ../deps/v8/gypfiles; mkdir -p /usr/ports/www/node10/work/node-v10.13.0/out/Release/obj/gen/torque-generated; "/usr/ports/www/node10/work/no
de-v10.13.0/out/Release/torque" ../src/builtins/base.tq ../src/builtins/array.tq ../src/builtins/typed-array.tq -o "/usr/ports/www/node10/work/node-v10.13.0/out/Rel
ease/obj/gen/torque-generated"
gmake[3]: *** [deps/v8/gypfiles/v8_torque.host.mk:17: f83d073c12b622af305dd74b713a0eb672e0bcba.intermediate] Illegal instruction (core dumped)
gmake[3]: *** Deleting file 'f83d073c12b622af305dd74b713a0eb672e0bcba.intermediate'
gmake[2]: *** [Makefile:99: node] Error 2
gmake[2]: Leaving directory '/usr/ports/www/node10/work/node-v10.13.0'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/node10
*** Error code 1

Stop.
make: stopped in /usr/ports/www/node10

===>>> make build failed for www/node10
===>>> Aborting update
</SNIP>
Comment 1 Jens Nykaer 2018-11-08 11:49:40 UTC
(In reply to Jens Nykaer from comment #0)

Tested on other hardware - same specs.  Yields same result
Comment 2 Bradley T. Hughes freebsd_committer 2019-01-24 05:32:20 UTC
The "Illegal instruction (core dumped)" makes me wonder what kind of hardware you are building on... can you attach your /var/run/dmesg.boot so I can have a look at the CPU features?
Comment 3 Bradley T. Hughes freebsd_committer 2019-03-12 21:39:51 UTC
Hi again,

I am still wondering what kind of hardware you are building on. Note that Node.js (V8, actually) requires a CPU with SSE2 and CMOV support, as can be seen here:

https://github.com/nodejs/node/blob/v10.15.3/deps/v8/src/ia32/assembler-ia32.cc#L128-L129

If your CPU doesn't have these, then that explains the SIGILL you are seeing.
Comment 4 Walter Schwarzenfeld freebsd_triage 2019-08-13 12:04:05 UTC
More than 6 month no answer from reporter. Feedback timeout.