All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14936] New: nodejs does not build
Date: Sun, 31 Jul 2022 12:57:09 +0000	[thread overview]
Message-ID: <bug-14936-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 14936
           Summary: nodejs does not build
           Product: buildroot
           Version: 2022.05.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: htenberge@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

When building with 2022.05.1 for a Raspberry Pi (32 bit) I get the following
error during the build:

ninja -C out/Release 
ninja: Entering directory `out/Release'
ninja: error: obj.host/tools/v8_gypfiles/run_torque.ninja:1271: multiple rules
generate gen/torque-generated/bit-fields.h [-w dupbuild=err]

make[2]: *** [Makefile:127: node] Error 1
make[1]: *** [package/pkg-generic.mk:293:
/home/harry/dev/ROPIEEE/ropieee-buildroot/build/nodejs-16.15.0/.stamp_built]
Error 2
make: *** [Makefile:23: _all] Error 2

This issue (or similar is reported here as well: 

https://github.com/nodejs/node/issues/37441


However, the fix does not work.

-- 
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:[~2022-07-31 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 12:57 bugzilla [this message]
2022-08-01 20:48 ` [Buildroot] [Bug 14936] nodejs does not build bugzilla
2022-08-02 20:39 ` bugzilla
2022-08-20  6:58 ` bugzilla
2022-08-23 20:57 ` bugzilla
2022-10-25 20:20 ` 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-14936-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.