[Pkg-javascript-devel] Bug#994245: nodejs: improve bootstraping nodejs

[Bo YU]

On Thu, Mar 24, 2022 at 01:11:40AM +0100, Jérémy Lal wrote:
>   On Thu, Mar 24, 2022 at 1:05 AM Jérémy Lal <[1]kapouer at melix.org>
>   wrote:
...
>
>     Followup-For: Bug #994245
>     X-Debbugs-Cc: Bo YU <[11]tsu.yubo at gmail.com>
>     Hi,
>     recently Bo YU has worked on building nodejs 14 for riscv64.
>     Bo, you can tell us here what you achieved, and what's blocking you
>     right now ?
>
>   Good news: I am building the nodejs(16.14) that remove d/control file
>   about nocheck nodoc  nobuildt tags
>    with ` sudo sbuild --arch=riscv64 -d sid-riscv64-sbuild
>   --extra-package=/home/vimer/pre_install_debs/`.
>   Yadd hinted me: I firstly rebuild pkg-js-tools package and yadd told me
>   that is all arch  and it does not need to
>   rebuild at all. So I downloaded those special packages
>   form [12]https://packages.debian.org/ and pass them
>   with --extar-package argument. At last it can build. But according to
>   last build experience, It will last 15+ h.
>   If everything is ok, I will upload the changes file to experimental
>   tomorrow
>
>   It's so simple it's painful :)
>
>   Well actually i got blinded by that simplicity, see below.
>
>   Bad news:
>   In the past two days, I got the same error when rebuild riscv arch
>   nodejs package:
>   if [ -x /<<PKGBUILDDIR>>/./node ] && [ -e /<<PKGBUILDDIR>>/./node ];
>   make: *** [debian/rules:186: binary] Error 2
...
>   dpkg-buildpackage: error: debian/rules binary subprocess returned exit
>   status 2
>   -----------------------------------------------------------------------
>   ---------
>   Build finished at 2022-03-15T18:52:50Z
>   Was I missing the dependencies?
>
>   I repeat that to bootstrap nodejs you need to build first the
>   arch-dependent packages (nodejs, libnode..)
>   --build=any
>   DEB_BUILD_PROFILES="nodoc nocheck nobuiltin"
>
>   let me just clarify. First  I git clone nodejs from salsa && git
>   checkout master-16.x
>   `dpkg-buildpackage --build=any` (with DEB_BUILD_PROFILES="nodoc nocheck
>   nobuiltin"). I am not sure whether
>   to fix d/control file.
>
>   Yes, the command is
>   DEB_BUILD_PROFILES="nodoc nocheck nobuiltin"  dpkg-buildpackage
>   --build=any
>
>     Hi,
>     After several times build fails about (on riscv hardware):
>      collect2: fatal error: ld terminated with signal 9 [Killed]
>     compilation terminated.
>
>   Linking nodejs happens to use a lot of memory: make sure enough swap
>   space is available.
>   (I had similar crashes with 12GB of RAM and no swap).
>   Or the linker is broken on riscv64... let's hope it is not.
>   If you happen to reach the "building deb" stage, you can disable
>   -dbgsym package creation,
>   which is very long, with another build profile: noautodbgsym.
>   DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym pkg.nodejs.nobuiltin"
Ok, good explations for newbie :-)
I am ready a high performance PC to build.

PS: I reply mail sometime via gmail web client. It is hard to move cursor
to buttom of mail body :-(. And I will noticed this issue from now.

Thanks all.

BR,
Bo

>   Jérémy
>
>References
>
>   1. mailto:kapouer at melix.org
>   2. mailto:tsu.yubo at gmail.com
>   3. mailto:tsu.yubo at gmail.com
>   4. mailto:kapouer at melix.org
>   5. mailto:tsu.yubo at gmail.com
>   6. mailto:kapouer at melix.org
>   7. mailto:tsu.yubo at gmail.com
>   8. mailto:kapouer at melix.org
>   9. mailto:tsu.yubo at gmail.com
>  10. mailto:kapouer at melix.org
>  11. mailto:tsu.yubo at gmail.com
>  12. https://packages.debian.org/