newlib 3.0.0

Question

newlib 3.0.0

jsanchezv opened this issue 6 years ago · comments

Hi Stephan,

I've found that isn't possible to compile C++ applications using the 8.2.1 gcc version (from https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads). I guess that the problem can be solved upgrading newlib to 3.0.0. Any plans for this?

Stephan Mühlstrasser · Answer 1 · Fri Dec 07 2018 05:19:30 GMT+0800 (China Standard Time)

Hi José,

can you please be more concrete what the problems are with gcc 8.2.1? What are the reasons that you need to move to gcc 8.2.1?

An upgrade to newlib 3.0.0 is of course possible, but it will probably have to wait until early 2019 when I have more time.

José Luis Sánchez · Answer 2 · Fri Dec 07 2018 23:43:14 GMT+0800 (China Standard Time)

Hi Stephan,

I'm doing a bit of experimentation with last gcc released by ARM, no more.

When I try to compile an application that uses libstdc++ I get many errors, some related to 'errno' variable by example.

My application compiles perfectly using gcc 7.3.1, so I don't have any problem with waiting until next year. But your circle-stdlib project is a precious gift for Circle and I hope that you want support it for long time.

Thanks by your hard work in circle-stdlib.

José Luis Sánchez · Answer 3 · Sun Dec 09 2018 21:05:11 GMT+0800 (China Standard Time)

Hi Stephan,

I've found that I can't compile my app using gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2 toolchain, I suspect that because is newlib 3.0.0 based. I'm using Linaro toolchain (https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/arm-eabi/gcc-linaro-7.3.1-2018.05-x86_64_arm-eabi.tar.xz) that is newlib-2.5.0 based.

I guess that ARM toolchain is unusable to compile full libc/libm/libstdc++ apps.

Rene Stange · Answer 4 · Sun Dec 09 2018 23:05:20 GMT+0800 (China Standard Time)

I am answering, because I prepared an tested the last release. The samples build and run successfully here, when built with both gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2 from the ARM developer website and with the Linaro toolchain, you have referenced in your comment.

Your application must have special requirements. We need more information. What error messages do you get? Can you provide a test program, which shows the problem?

Yes, the circle-stdlib support depends on the used toolchain, but it is tested and should work at least with the recommended toolchain from the ARM developer website.

José Luis Sánchez · Answer 5 · Mon Dec 10 2018 01:57:33 GMT+0800 (China Standard Time)

It's easy start to get compilation errors:

1.- Go to samples/02-stdio-hello directory.
2.- Edit kernel.h and add a line with "#include " and save the file
3.- Compile

Rene Stange · Answer 6 · Mon Dec 10 2018 03:46:10 GMT+0800 (China Standard Time)

I tried it with gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2. No errors. Are you sure, your build environment is all right? Please be sure to use ./build.bash -c before configure and make.

Rene Stange · Answer 7 · Fri Mar 01 2019 18:28:10 GMT+0800 (China Standard Time)

There has been a modification in Circle 39, which is included in the latest release of this circle-stdlib project, which should fix include issues. It depended on the kind and order of included headers, if compilation errors arose.

Stephan Mühlstrasser · Answer 8 · Sat Mar 02 2019 22:13:25 GMT+0800 (China Standard Time)

I verified that I can build circle-stdlib v8.0 with gcc-arm-8.2-2019.01-x86_64-arm-eabi downloaded from https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads. The four sample programs 01-nosys, 02-stdio-hello, 03-stdio-fatfs and 04-std run successfully in QEMU.
So apparently it is unnecessary to update newlib currently to a newer version for building with the most recent ARM gcc, and as an update of newlib could potentially have an impact on whether a build with older toolchains is still possible I'm closing this issue without action.