-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
V8 will remove the MIPS(64) port #26179
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Note that the MIPS port has already been broken for a while. |
Upstream V8 is dropping support for mips/mipsel/mips64/mips64el. This commit removes the build flags from the configure script and some loose ends from the documentation. Fixes: nodejs#26179
FYI @nodejs/distros |
I did see the announcement but thanks for the reminder. :-) We don't claim to support mips(64)(el) or test it regularly so I think it's just a matter of dropping it from the build scripts: #26192 |
I actually have node@8 running in OpenWRT on a TP-Link Archer C7 (CPU is a Qualcomm Atheros QCA9558) patched using https://github.com/openwrt/packages/tree/master/lang/node. |
Also cc @kapouer based on previous issues raised re. MIPS. |
One of the problems here is that Firefox currently has a hard build dependency on |
I think that would be preferable. Do you have the option to cross-compile? |
@refack https://github.com/nxhack/openwrt-node-packages/tree/master/node |
FYI, it currently looks like another company is stepping up to maintain the MIPS(64) port modulo Big Endian. I will keep you posted. |
@natorion link or reference? Thanks in advance. |
See the linked thread: https://groups.google.com/forum/#!topic/v8-dev/oXkv5OVCXyc |
Currently under active maintenance is loongson CPU. They use mips architecture and the company is well-funded. A large number of orders have been obtained, and there will be a lot of mips demand in the next few years (in China) |
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 nodejs/node#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>
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 nodejs/node#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> (cherry picked from commit 69d3116) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This is in the context of https://groups.google.com/forum/#!topic/v8-dev/oXkv5OVCXyc.
As nobody stepped up to maintain the ports, V8's current plan is to remove the MIPS(64) ports from the V8 codebase with V8 7.5 (~ mid March 2019).
As MIPS(64) is also not supported in Node.js (https://github.com/nodejs/node/blob/master/BUILDING.md#supported-platforms-1), I don't know if this is really relevant to you folks at all? Please speak up if this is not the case.
The text was updated successfully, but these errors were encountered: