RE: devel/arm-none-eabi-newlib headers inconsistencies (not functional) or am I misusing something?
- Reply: Mark Millard : "Re: devel/arm-none-eabi-newlib headers inconsistencies (not functional) or am I misusing something?"
- Reply: José_Pérez : "Re: devel/arm-none-eabi-newlib headers inconsistencies (not functional) or am I misusing something?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 26 May 2023 19:32:50 UTC
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 > > #include <stdio.h> > > int main(int argc, char *argv[]) { > return 0; > } > > % arm-none-eabi-gcc break_arm.c > . . . list of errors and such . . . 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. (arm-none-eabi-gcc is not limited to use of arm-none-eabi-newlib and arm-none-eabi-newlib is not a default binding for arm-none-eabi-gcc so far as I can tell.) In other words, if you did not have devel/arm-none-eabi-newlib installed, and tried the "arm-none-eabi-gcc break_arm.c" command, I'd expect the same results that you report: arm-none-eabi-newlib is simply not being used at all, if I understand right. Looks like you need to figure out how to tell arm-none-eabi-gcc to use the arm-none-eabi-newlib materials. (Not something I've ever done.) === Mark Millard marklmi at yahoo.com