When it is a porting issue rather than a buildd issue, it's better to contact the porter list. Doing so.
----- Message transféré de Jérémy Lal <[email protected]> ----- From: Jérémy Lal <[email protected]> To: [email protected] Date: Wed, 15 Jun 2022 19:35:20 +0200 Subject: Re: failed mipsel build of nodejs 18.3.0+dfsg-1 Message-ID: <CAJxTCxxEwZv2aSB8=ygwtsf5kq_ky5hsokscj-9yofxmwhh...@mail.gmail.com> I opened an issue upstream, feel free to give any info directly there: https://github.com/nodejs/node/issues/43435 Le mer. 15 juin 2022 à 18:50, Jérémy Lal <[email protected]> a écrit : > Hi, > > Compiling nodejs 18.3.0 gives this error on mipsel (see log below): > > Error: float register should be even, was 13 > > I fixed it with the patch below, but I don't know what I'm doing there, > so it would be safer if someone with better knowledge could review it: > > --- a/deps/v8/src/codegen/mips/register-mips.h > +++ b/deps/v8/src/codegen/mips/register-mips.h > @@ -32,9 +32,8 @@ > // Currently, MIPS just use even float point register, except > // for C function param registers. > #define DOUBLE_USE_REGISTERS(V) \ > - V(f0) V(f2) V(f4) V(f6) V(f8) V(f10) V(f12) V(f13) \ > - V(f14) V(f15) V(f16) V(f18) V(f20) V(f22) V(f24) V(f26) \ > - V(f28) V(f30) > + V(f0) V(f2) V(f4) V(f6) V(f8) V(f10) V(f12) V(f14) \ > + V(f16) V(f18) V(f20) V(f22) V(f24) V(f26) V(f28) V(f30) > > #define FLOAT_REGISTERS DOUBLE_REGISTERS > #define SIMD128_REGISTERS(V) \ > > > Thanks, > Jérémy > > ---------- Forwarded message --------- > De : Debian buildds <[email protected]> > Date: mer. 15 juin 2022 à 15:15 > Subject: failed mipsel build of nodejs 18.3.0+dfsg-1 > To: <[email protected]> > > > * Source package: nodejs > * Version: 18.3.0+dfsg-1 > * Architecture: mipsel > * State: failed > * Suite: experimental > * Builder: mipsel-osuosl-03.debian.org > * Build log: > https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=mipsel&ver=18.3.0%2Bdfsg-1&stamp=1655298344&file=log > > Please note that these notifications do not necessarily mean bug reports > in your package but could also be caused by other packages, temporary > uninstallabilities and arch-specific breakages. A look at the build log > despite this disclaimer would be appreciated however. > ----- Fin du message transféré ----- -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net
