>> but how compiler know, that FPU is present or absent (-CfSOFT)?
>
> armel has by default no fpu or whatever.

Thx

>
>>
>>
>>> needed nor desired. -dFPC_ARMEL is enough. Neither is -dFPC_ARMEL
>>> needed
>>>  in CROSSOPT. It is only needed when the first arm compiler is built
>>> and
>>> in this case OPT=-dFPC_ARMEL is enough.
>>>
>> for me better:  CPU_TARGET=armel  (similar as ARMEB)
>
> Neither armel nor armeb are supported yet by fpc. So the extra
> OPT=-dFPC_ARMEL is needed when building fpc.

OK.

Can I ask:
What is difference between CPU_TARGET=arm (with -CaEABI) and armel
seems, that first not produce proper EABI code though it say it is
(readelf status)
its normal or bug or unexpected behaviour ?


Darek


--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply via email to