[En-Nut-Discussion] Stdlib.h unsetenv declaration error

Ulrich Prinz uprinz2 at netscape.net
Wed May 18 21:37:35 CEST 2011


Hi Gregor,

sorry for your inconvenience. The problem was that two issues run into
each other. First we didn't get the right point to jump from arm-elf- to
arm-none-eabi-. Then the compiler got tweaked to be much more precise on
code inspection.
And that all happened while developing the system from 4.8.x to 4.9.x.

On the other hand we have lots of industrial users ( the thing that
Nut/OS was initially made for) and they have... sort of respect to
upgrade to new unverified tools.
We could add dozens of new compiler variations to the nutconf tool
arm-elf-gcc-arm
arm-elf-gcc-arm-debug
arm-elf-gcc-cm3
arm-elf-gcc-cm3-debug
arm-none-eabi-gcc
arm-none-eabi-gcc-debug
...
I think this will confuse the beginners as they will surely try the
wrong thing first.

So the deal is to set a breakpoint, update manuals and do a full
release. If it doesn't get into the 4.9.0 it will be in 4.10.
As 4.10 will have CortexM support it must have gcc 4.5.x/4.6.x and so it
must use arm-none-eabi-
But I am pretty sure we have it in 4.9.0.

you normally do not have to change any _EXFUN() function. Just use
nutconf to switch the right button as Ole told you before.

Then take a look at the trunk instead of the last release version. Most
if not all of your problems are already fixed there.
The trunk is actually right in front of being release. Harald is working
on that.
> 
> I know that Nut/OS is a good system and designed to work with Yagarto, 
> therefore think that I am doing something wrong. Could someone point 
> out my mistake please.
> 
You didn't do anything wrong, just hit a bad timing point :)

Ulrich



More information about the En-Nut-Discussion mailing list