Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15823] New: Installing nodejs modules with native extensions fails on first run
Date: Wed, 25 Oct 2023 20:38:54 +0000	[thread overview]
Message-ID: <bug-15823-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15823

            Bug ID: 15823
           Summary: Installing nodejs modules with native extensions fails
                    on first run
           Product: buildroot
           Version: 2023.08.2
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: marcus.hoffmann@othermo.de
                CC: buildroot@uclibc.org
  Target Milestone: ---

I'm building the the raspberrypi4_64_defconfig with the following
changes/additions:

```
BR2_CCACHE=y
BR2_PACKAGE_NODEJS=y
BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL="serialport"
BR2_TARGET_ROOTFS_EXT2_SIZE="300M"
```


This fails during the first run with the following errors:
```
ERROR: architecture for
"/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm/node.napi.armv6.node"
is "ARM", should be "AArch64"
ERROR: architecture for
"/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cpp/prebuilds/android-arm/node.napi.armv7.node"
is "ARM", should be "AArch64"
ERROR: architecture for
"/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm/node.napi.armv7.node"
is "ARM", should be "AArch64"
ERROR: architecture for
"/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.glibc.node"
is "Advanced Micro Devices X86-64", should be "AArch64"
ERROR: architecture for
"/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.musl.node"
is "Advanced Micro Devices X86-64", should be "AArch64"
make[1]: *** [package/pkg-generic.mk:406:
/home/marcus/repos/buildroot-upstream/output/build/nodejs-16.20.0/.stamp_installed]
Error 1
```

On a second invocation of make, it then succeeds to build. I have not yet
runtime testing if the serialport library actually works.

As discussed on IRC just now, there was a discussion about this issue on this
patch already:

https://patchwork.ozlabs.org/project/buildroot/patch/20190531075800.7064-1-vcrini@gmail.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-10-25 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 20:38 bugzilla [this message]
2023-10-25 20:43 ` [Buildroot] [Bug 15823] Installing nodejs modules with native extensions fails on first run bugzilla
2023-10-27 10:43 ` bugzilla
2023-10-31 12:09 ` bugzilla
2023-11-07 21:44 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15823-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox