<div dir="ltr"><div dir="ltr">hi,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 25, 2022 at 9:31 AM Jérémy Lal <<a href="mailto:kapouer@melix.org">kapouer@melix.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 25, 2022 at 12:55 AM Jérémy Lal <<a href="mailto:kapouer@melix.org" target="_blank">kapouer@melix.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 25, 2022 at 12:23 AM Jérémy Lal <<a href="mailto:kapouer@melix.org" target="_blank">kapouer@melix.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 25, 2022 at 12:17 AM Bo YU <<a href="mailto:tsu.yubo@gmail.com" target="_blank">tsu.yubo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 25, 2022 at 7:11 AM Bo YU <<a href="mailto:tsu.yubo@gmail.com" target="_blank">tsu.yubo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Mar 24, 2022 at 01:11:40AM +0100, Jérémy Lal wrote:<br>
> On Thu, Mar 24, 2022 at 1:05 AM Jérémy Lal <[1]<a href="mailto:kapouer@melix.org" target="_blank">kapouer@melix.org</a>><br>
> wrote:<br>
><br>
> --build=any<br>
...<br>
><br>
> Hi,<br>
> After several times build fails about (on riscv hardware):<br>
> collect2: fatal error: ld terminated with signal 9 [Killed]<br>
> compilation terminated.<br>
><br>
> Linking nodejs happens to use a lot of memory: make sure enough swap<br>
> space is available.<br>
> (I had similar crashes with 12GB of RAM and no swap).<br>
> Or the linker is broken on riscv64... let's hope it is not.<br>
> If you happen to reach the "building deb" stage, you can disable<br>
> -dbgsym package creation,<br>
> which is very long, with another build profile: noautodbgsym.<br>
> DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym pkg.nodejs.nobuiltin"<br>
> Jérémy<br>
Today I checkout master-16.x, and I got:<br></blockquote><div>sorry, add more useful info:</div>cc -o /home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o ../deps/llhttp/src/api.c '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CERT_STORE' '-D__STDC_FORMAT_MACROS' -I../deps/llhttp -I../deps/llhttp/include -pthread -Wall -Wextra -Wno-unused-parameter -fPIC -O3 -fno-omit-frame-pointer -MMD -MF /home/vimer/git/nodejs/out/Release/.deps//home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o.d.raw -fPIC -g -fPIC -g -fPIC -g -fPIC -g -c<br>make[3]: *** No rule to make target '../deps/acorn/acorn/dist/acorn.js', needed by '/home/vimer/git/nodejs/out/Release/obj/gen/node_javascript.cc'. Stop.</div></div></blockquote><div><br></div><div>Maybe some symlink is missing, am checking it but it will take a while to rebuild.</div></div></div></blockquote><div><br></div><div>I pushed a fix for a mistake in debian/rules that happened while renaming "nobuiltin".</div></div></div></blockquote><div><br></div><div>At least it builds and produces deb packages here on amd64 without depending on nodejs itself.<br></div><div><br></div></div></div></blockquote><div>It have finished about compiling phrase, but dh_missing reports error:</div><div>make[1]: Entering directory '/home/vimer/git/nodejs'<br>make[1]: awk: No such file or directory<br>make[1]: awk: No such file or directory<br>sed 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' debian/libnode.install > debian/libnode.install<br>sed -e 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' -e 's/@ABI@//g' debian/<a href="http://libnode-dev.links.in">libnode-dev.links.in</a> > debian/libnode-dev.links<br>cp debian/<a href="http://nodejs.install.in">nodejs.install.in</a> debian/nodejs.install<br>echo "./lib /usr/share/nodejs/node/" >> debian/nodejs.install<br>deps_files="deps/v8/tools/splaytree.mjs deps/v8/tools/codemap.mjs deps/v8/tools/consarray.mjs deps/v8/tools/csvparser.mjs deps/v8/tools/profile.mjs deps/v8/tools/profile_view.mjs deps/v8/tools/logreader.mjs deps/v8/tools/arguments.mjs deps/v8/tools/tickprocessor.mjs deps/v8/tools/sourcemap.mjs deps/v8/tools/tickprocessor-driver.mjs deps/acorn/acorn/dist/acorn.js deps/acorn/acorn-walk/dist/walk.js deps/cjs-module-lexer/lexer.js"; \<br>for src in $deps_files; do \<br> dst=`dirname $src`; \<br> echo "./$src /usr/share/nodejs/node/$dst" >> debian/nodejs.install; \<br>done<br># and add uncompiled acorn<br>echo "./node-acorn/acorn/src /usr/share/nodejs/node/deps/acorn/acorn/" >> debian/nodejs.install<br>echo "./node-acorn/acorn-walk/src /usr/share/nodejs/node/deps/acorn/acorn-walk/" >> debian/nodejs.install<br>dh_install<br>make[1]: Leaving directory '/home/vimer/git/nodejs'<br> debian/rules override_dh_installdocs<br>make[1]: Entering directory '/home/vimer/git/nodejs'<br>dh_installdocs<br>find debian/nodejs-doc/usr/share/doc/nodejs-doc -name *.json -delete || true<br>find: 'debian/nodejs-doc/usr/share/doc/nodejs-doc': No such file or directory<br>make[1]: Leaving directory '/home/vimer/git/nodejs'<br> dh_installchangelogs -a<br> dh_installman -a<br> dh_lintian -a<br> dh_perl -a<br> dh_link -a<br> dh_strip_nondeterminism -a<br> dh_compress -a<br> dh_fixperms -a<br> dh_missing -a<br>dh_missing: warning: usr/lib/libnode.so.93 exists in debian/tmp but is not installed to anywhere<br> The following debhelper tools have reported what they installed (with files per package)<br> * dh_install: libnode-dev (179), libnode93 (0), nodejs (72), nodejs-doc (0)<br> * dh_installdocs: libnode-dev (0), libnode93 (0), nodejs (0), nodejs-doc (0)<br> * dh_installman: libnode-dev (0), libnode93 (0), nodejs (1), nodejs-doc (0)<br> If the missing files are installed by another tool, please file a bug against it.<br> When filing the report, if the tool is not part of debhelper itself, please reference the<br> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+).<br> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)<br> Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built<br> If the omission is intentional or no other helper can take care of this consider adding the<br> paths to debian/not-installed.<br>dh_missing: error: missing files, aborting<br>make: *** [debian/rules:186: binary-arch] Error 255<br>dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2<br></div><div><br></div><div>Will fix debian/not-installed？</div><div>BTW, We have sole cmd execute after dh_missing phrase? if not rebuilt again it will save many times.</div><div>Bo</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div>Jérémy</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>
</blockquote></div></div>
</blockquote></div></div>