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

El 2023-05-27 12:18, Mark Millard escribió:
>> should be fixed or is it ok
>> to leave it as it is now?
> 
> Leave it as it is.

Ok.

> You need
> /usr/local/lib/gcc/arm-none-eabi to be first (or
> the only entry).
> 

If I force the search path to use /usr/local/arm-none-eabi/include
only, it does not work:
% arm-none-eabi-gcc -nostdinc -I/usr/local/arm-none-eabi/include 
break_arm.c
In file included from /usr/local/arm-none-eabi/include/stdio.h:35,
                  from break_arm.c:1:
/usr/local/arm-none-eabi/include/sys/cdefs.h:45:10: fatal error: 
stddef.h: No such file or directory
    45 | #include <stddef.h>
       |          ^~~~~~~~~~
compilation terminated.

If I add arm gcc port paths AFTER newlib path, it works:
% arm-none-eabi-gcc -nostdinc -I/usr/local/arm-none-eabi/include 
-I/usr/local/lib/gcc/arm-none-eabi/11.3.0/include 
-I/usr/local/lib/gcc/arm-none-eabi/11.3.0/include-fixed -c break_arm.c 
&& echo done
done

Shall the include path be swapped in the arm gcc port?

We shall also evaluate whether the system defaul /usr/include shall
be left as a last resort or not.

BR,

-- 
José Pérez