From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Daniel Price <daniel.price@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Martin Bark <martin@barkynet.com>
Subject: Re: [Buildroot] [PATCH] package/nodejs: drop support for the MIPS architecture
Date: Wed, 09 Nov 2022 14:28:31 +0100 [thread overview]
Message-ID: <87leokfe9s.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221026175705.3928406-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Wed, 26 Oct 2022 19:57:05 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> The build of NodeJS fails on mipsel due to an issue in the V8 code:
> ../../deps/v8/src/compiler/backend/mips/code-generator-mips.cc:4106:48: error: call of overloaded 'Operand(int64_t)' is ambiguous
> 4106 | Operand(static_cast<int64_t>(0)));
> There is apparently a lack of maintenance of the MIPS port of V8, as
> is discussed in the Github issue at
> https://github.com/nodejs/node/issues/26179.
> Until this get improved/fixed, our best option is to drop support for
> MIPS in our NodeJS package.
> Fixes:
> http://autobuild.buildroot.net/results/0e6ee80c77bcb77afe18410e8d9da93b738cb0a4/
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
:/
Committed to 2022.08.x, thanks.
Perhaps this is only a >= nodejs 16.x issue? We don't seem to have any
similar build issues for 14.x on 2022.02.x.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-09 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 17:57 [Buildroot] [PATCH] package/nodejs: drop support for the MIPS architecture Thomas Petazzoni via buildroot
2022-10-30 11:10 ` Thomas Petazzoni via buildroot
2022-11-09 13:28 ` Peter Korsgaard [this message]
2022-11-09 16:00 ` Thomas Petazzoni via buildroot
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=87leokfe9s.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=martin@barkynet.com \
--cc=thomas.petazzoni@bootlin.com \
/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