From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14451] nodejs won't build on Fedora 35
Date: Wed, 22 Dec 2021 14:10:42 +0000 [thread overview]
Message-ID: <bug-14451-163-L89SexZSJe@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14451-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14451
--- Comment #3 from Fabrice Fontaine <fontaine.fabrice@gmail.com> ---
The following patch should fix this issue:
https://patchwork.ozlabs.org/project/buildroot/patch/20211222140737.1179968-1-fontaine.fabrice@gmail.com/
Moreover, python 3.10 support has been added to nodejs 14.18.2:
https://github.com/nodejs/node/releases/tag/v14.18.2
--
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
next prev parent reply other threads:[~2021-12-22 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 10:00 [Buildroot] [Bug 14451] New: nodejs won't build on Fedora 35 bugzilla
2021-12-13 16:27 ` [Buildroot] [Bug 14451] " bugzilla
2021-12-14 19:03 ` bugzilla
2021-12-14 19:06 ` [Buildroot] [PATCH 1/1] package/mesa3d: don't disable DRI3 for some Gallium drivers Michael Taubert
2021-12-16 17:28 ` Arnout Vandecappelle
2021-12-16 18:26 ` Michael Taubert
[not found] ` <aafcded5-c0f4-4745-a226-da57d0e7a805__41403.4441857197$1639675757$gmane$org@mind.be>
2021-12-16 18:12 ` Bernd Kuhls
2021-12-16 18:33 ` Arnout Vandecappelle
2021-12-16 21:45 ` Peter Seiderer
2021-12-17 10:15 ` Michael Taubert
2021-12-22 14:10 ` bugzilla [this message]
2022-01-09 16:28 ` [Buildroot] [Bug 14451] nodejs won't build on Fedora 35 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-14451-163-L89SexZSJe@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.