You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I fixed the build at least on Linux with nodejs/node@4ba0b28 and nodejs/node@ac8fb3f.
Let's keep this issue open because cppgc is still a moving target and I did not look into implementing the build options that it provides.
19:41:52 python ./configure --verbose --dest-cpu=arm
19:41:55 gyp: Dependency '/home/iojs/build/workspace/node-cross-compile/tools/v8_gypfiles/v8.gyp:cppgc_base#host' not found while trying to load target /home/iojs/build/workspace/node-cross-compile/tools/v8_gypfiles/v8.gyp:v8_base_without_compiler#host
And macOS:
19:41:43 running:
19:41:43 python tools/gyp_node.py --no-parallel -Dconfiguring_node=1 -f make-mac
19:41:43 static library v8_base_without_compiler has several files with the same basename:
19:41:43 allocation: ../../deps/v8/src/utils/allocation.cc ../../deps/v8/src/heap/cppgc/allocation.cc
19:41:43 free-list: ../../deps/v8/src/heap/free-list.cc ../../deps/v8/src/heap/cppgc/free-list.cc
19:41:43 sweeper: ../../deps/v8/src/heap/sweeper.cc ../../deps/v8/src/heap/cppgc/sweeper.cc
19:41:43 heap: ../../deps/v8/src/heap/heap.cc ../../deps/v8/src/heap/cppgc/heap.cc
19:41:43 libtool on OS X will generate warnings for them.
19:41:43 Error running GYP
19:41:43 make: *** [build-ci] Error 1
And Windows:
19:46:05 cpp-heap.cc
19:46:05 C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\include\xutility(3778,16): error C2280: 'std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>> &std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>>::operator =(const std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>> &)': attempting to reference a deleted function [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
19:46:05 C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\include\memory(1917): message : see declaration of 'std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>>::operator =' [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
19:46:05 C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\include\memory(1917,17): message : 'std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>> &std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>>::operator =(const std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>> &)': function was explicitly deleted [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
19:46:05 C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\include\vector(1127): message : see reference to function template instantiation '_OutIt *std::_Copy_unchecked<_Iter,std::unique_ptr<cppgc::internal::BaseSpace,std::default_delete<cppgc::internal::BaseSpace>>*>(_InIt,_InIt,_OutIt)' being compiled [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
@mhdawson It's a new mark and sweep GC called Oilpan. It does scanning of C++/JS objects (treats them as one heap). It's actively being worked on and any port to other platforms will also get ported to p/z linux and AIX: https://chromium-review.googlesource.com/c/v8/v8/+/2144691
Activity
[-]cppgc[/-][+]Port cppgc config to gyp[/+]tools: add cppgc_base and v8_cppgc_shared to v8.gyp
gyp: disable duplicate basename check
targos commentedon Jun 24, 2020
I fixed the build at least on Linux with nodejs/node@4ba0b28 and nodejs/node@ac8fb3f.
Let's keep this issue open because cppgc is still a moving target and I did not look into implementing the build options that it provides.
tools: add cppgc_base and v8_cppgc_shared to v8.gyp
gyp: disable duplicate basename check
targos commentedon Jun 24, 2020
CI: https://ci.nodejs.org/job/node-test-commit-node-v8/546/
Need to fix cross-compilation:
And macOS:
And Windows:
/cc @nodejs/v8
ryzokuken commentedon Jun 24, 2020
The ARM issue doesn't look like a platform-specific error?
tools: add cppgc_base and v8_cppgc_shared to v8.gyp
gyp: disable duplicate basename check
tools: add cppgc_base and v8_cppgc_shared to v8.gyp
gyp: disable duplicate basename check
gengjiawen commentedon Jun 26, 2020
tools: add cppgc_base and v8_cppgc_shared to v8.gyp
gyp: disable duplicate basename check
100 remaining items
mhdawson commentedon Sep 9, 2020
@miladfarca could you take a look at cppgc so we understand how it might impact power/s390 in the future?
vsemozhetbyt commentedon Sep 11, 2020
nodejs/gyp-next#60 seems fixed but there are no canaries at all for last days.
targos commentedon Sep 11, 2020
Canary needed an update in
v8.gyp. I'm testing it locally.Edit: should be fine tomorrow if V8 doesn't introduce another breaking change.
miladfarca commentedon Sep 12, 2020
@mhdawson It's a new mark and sweep GC called
Oilpan. It does scanning of C++/JS objects (treats them as one heap). It's actively being worked on and any port to other platforms will also get ported to p/z linux and AIX:https://chromium-review.googlesource.com/c/v8/v8/+/2144691
This also eliminates the use of a clang plugin: nodejs/node#27257 (comment)
V8 issue for tracing: https://bugs.chromium.org/p/chromium/issues/detail?id=1056170
vsemozhetbyt commentedon Sep 13, 2020
Something seems break all builds again. IIUC, #167
vsemozhetbyt commentedon Sep 14, 2020
Still no Windows in today's build(
targos commentedon Sep 14, 2020
@vsemozhetbyt there's a build failure in release CI, but it seems unrelated to this issue. I opened #172
mhdawson commentedon Sep 14, 2020
@miladfarca thanks for the clarification :)
gengjiawen commentedon Sep 17, 2020
@vsemozhetbyt windows fix got merged, binary should be on the way 🎁
vsemozhetbyt commentedon Sep 17, 2020
Thank you all! Win-x64 is back.
Now I can publish my translation about Intl.Segmenter (shipped in V8 87) and link to the full binaries set for readers to test the feature)
Are Win-x86 binaries not built anymore or is this a build issue? There were ones in the last successful build.
targos commentedon Sep 17, 2020
x86 build still fails:
gengjiawen commentedon Sep 17, 2020
@targos looks like you forget the patch x32 to ia32 in
v8.gypfrom v8 8.5.targos commentedon Sep 18, 2020
@gengjiawen right, good catch! I pushed the change to canary-base. Build should go well tomorrow.
gengjiawen commentedon Oct 20, 2020
V8 8.6 merged into core 🎁