Re: devel/arm-none-eabi-newlib headers inconsistencies (not functional) or am I misusing something?

El 2023-05-26 21:32, Mark Millard escribió:
> José_Pérez <fbl_at_aoek.com> wrote on
> Date: Fri, 26 May 2023 16:53:15 UTC :
> 
>> a source as simple as this does not compile with
>> devel/arm-none-eabi-newlib installed
...
> 
> Looks like you did nothing to tell arm-none-eabi-gcc
> to use arm-none-eabi-newlib materials . It will not
> do so automatically from what I can tell.

It does so automatically, in fact the directories where
devel/arm-none-eabi-newlib stores headers is in the search
path of arm-none-eabi-gcc:
% arm-none-eabi-gcc -xc -E -v -
Using built-in specs.
...
#include "..." search starts here:
#include <...> search starts here:
  /usr/local/lib/gcc/arm-none-eabi/11.3.0/include
  /usr/local/lib/gcc/arm-none-eabi/11.3.0/include-fixed
  
/usr/local/lib/gcc/arm-none-eabi/11.3.0/../../../../arm-none-eabi/include
  /usr/include
End of search list.

In particular 
/usr/local/lib/gcc/arm-none-eabi/11.3.0/../../../../arm-none-eabi/include
is /usr/local/arm-none-eabi/include which is where 
devel/arm-none-eabi-newlib stores
headers.

The problem, as outlined in my first message, is that the
header files appears not to be coherent with themselves and I think
they need to be fixed somehow. I am calling for hints on how to fix 
them.

BR,

-- 
José Pérez