Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14936] nodejs does not build
Date: Tue, 23 Aug 2022 20:57:59 +0000	[thread overview]
Message-ID: <bug-14936-163-JhQKIQrZjQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14936-163@https.bugs.busybox.net/>

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

--- Comment #4 from Fabrice Fontaine <fontaine.fabrice@gmail.com> ---
This is none issue on nodejs side: https://github.com/nodejs/node/issues/37441
as spotted by Thomas in
https://patchwork.ozlabs.org/project/buildroot/patch/20220809075704.86472-4-ardeleanalex@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

  parent reply	other threads:[~2022-08-23 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 12:57 [Buildroot] [Bug 14936] New: nodejs does not build bugzilla
2022-08-01 20:48 ` [Buildroot] [Bug 14936] " bugzilla
2022-08-02 20:39 ` bugzilla
2022-08-20  6:58 ` bugzilla
2022-08-23 20:57 ` bugzilla [this message]
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-JhQKIQrZjQ@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