Re: nodejs on arm64 now in experimental
On Fri, Sep 11, 2015 at 3:51 AM, Jérémy Lal <kapouer@melix.org> wrote:
>
>
> 2015-09-11 10:48 GMT+02:00 Edmund Grimley Evans
> <edmund.grimley.evans@gmail.com>:
>>
>> This seems to be the problem on armel:
>>
>> configure: o['variables']['arm_fpu'] = 'vfpv2'
>>
>> It probably should be "vfp" instead of "vfpv2". A GCC man page says:
>>
>> -mfpu=name
>> -mfpe=number
>> -mfp=number
>> This specifies what floating point hardware (or hardware
>> emulation)
>> is available on the target. Permissible names are: fpa, fpe2,
>> fpe3, maverick, vfp, vfpv3, vfpv3-fp16, vfpv3-d16,
>> vfpv3-d16-fp16,
>> vfpv3xd, vfpv3xd-fp16, neon, neon-fp16, vfpv4, vfpv4-d16,
>> fpv4-sp-d16 and neon-vfpv4. -mfp and -mfpe are synonyms for
>> -mfpu=fpenumber, for compatibility with older versions of GCC.
>>
>> The absence of "vfpv2" from the list is a bit weird, but VFPv1 is
>> obsolete so perhaps VFPv2 was the only kind of VFP of interest at the
>> time they added the option to GCC.
>>
>> Edmund
>
>
>
> Indeed, i had a set of fixes in libv8-3.14 debian/rules, so i'll see how to
> apply
> them to nodejs as well.
vfpv2 was optional for armv6 and the rasbian port has it enabled by
default. If "armv7" is not selected, it's vfpv2/armv6...
https://github.com/nodejs/node/blob/master/configure#L607
Regards,
--
Robert Nelson
https://rcn-ee.com/
Reply to: