[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: nodejs 4.4.7 build failure with "linking mips:4000 module with previous mips:isa32 modules"



On Sun, Jul 3, 2016 at 7:30 PM, Jérémy Lal <kapouer@melix.org> wrote:
>
>
> 2016-07-03 13:24 GMT+02:00 YunQiang Su <wzssyqa@gmail.com>:
>>
>> On Sun, Jul 3, 2016 at 7:15 PM, James Cowgill <jcowgill@debian.org> wrote:
>> > On Sun, 2016-07-03 at 19:07 +0800, YunQiang Su wrote:
>> >> On Sun, Jul 3, 2016 at 6:13 PM, Jérémy Lal <kapouer@melix.org> wrote:
>> >> > Hi,
>> >> >
>> >> > i don't know what's the meaning of the errors at the end of:
>> >> >
>> >> > https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=mipsel&ver=4.4.7~dfsg-1&stamp=1467345231
>> >>
>> >> We just upgrade glibc to mips32 from mips2, and gcc-6 default to
>> >> mips32r2.
>> >> I guess it is due this bump.
>> >
>> > This would explain it. nodejs seems to be using '-mips3' but you cannot
>> > link mips3 code with mips32r2 code. Also, isn't mips3 a 64-bit ISA? Why
>> > is it being used on mipsel (which is 32-bit)?
>> >
>>
>> mips3 is also can be used for 32 bit.
>> It is just a revision.
>
>
> nodejs targets loongson (through v8) but it could target a higher set like
> mips32r1
> if needed.

Then can you have a try of mips32r2.
We are working on bump all to mips32r2.

>
> Jérémy



-- 
YunQiang Su


Reply to: