<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
OK, I dug for a minute and found this:<br>
<br>
<a class="moz-txt-link-freetext" href="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0475c/BAJFHFDI.html">http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0475c/BAJFHFDI.html</a><br>
<br>
If we click on the right side-middle link "ISO C Features missing
from microlib" the list is available. If "
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma,
Arial, Helvetica, sans-serif; font-size: small; font-style:
normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
display: inline !important; float: none; background-color:
rgb(255, 255, 255);"><span class="Apple-converted-space"> </span></span><code
class="literal" style="color: rgb(51, 51, 153); font-family:
'Lucida Sans Typewriter', 'Courier New', Courier, monospace;
font-size: 0.9em; margin-top: 0.4em; margin-bottom: 0.2em;
font-weight: normal; font-style: normal; font-variant: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">#pragma import(__use_full_stdio)" </code>is used then full
FILE* support is available except for feof() and ferror(). <br>
<br>
Seems like you just got very unlucky needing feof. The floating
point compromises could also be a major pain, but the other stuff
seems pretty minor (e.g. what would we expect to get out of a call
to system or getenv?)<br>
<br>
But it's good to know that "mbed compatible" does not imply "uniform
ISO C support". Please keep us posted on whether the Kinetis board<br>
<br>
About the "setting up a GNU toolchain". On Linux this is about as
easy as anything could get,and the mbed project export mechanism
dove tails with these tools beautifully.<br>
<br>
-Pete<br>
<br>
<br>
<div class="moz-cite-prefix">On 05/04/2016 01:31 PM, Alex Davis via
TriEmbed wrote:<br>
</div>
<blockquote
cite="mid:1462383076.2876962.598149673.383C717E@webmail.messagingengine.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">I'm curious what this means as well.
The Nucleo boards use Cortex-M[2,3,4,7] devices for which there is
plenty of support for in gcc ARM toolchains, as well as IAR, Keil, etc..
By "ARM C", do you mean Keil, which is owned by the ARM company? If so
that should be supported as well.
</pre>
</blockquote>
<pre wrap="">
Here's an example from developer.mbed.org:
<a class="moz-txt-link-freetext" href="https://developer.mbed.org/questions/3895/Compile-for-Nucleo-L053r8/">https://developer.mbed.org/questions/3895/Compile-for-Nucleo-L053r8/</a>
Someone's trying compile something that uses the SDFileSystem library.
They get an error on 'feof' (which is used to know when you reach EOF in
a file). This is the answer from MBED:
"I believe the application is for targets which use ARM C library, which
many nucleo does not support currently. They use uARM which implements
only subset of C library, therefore some functions are not available.
There's reference on ARM info pages , what is stripped."
So, that sucks. Wish they'd listed that somewhere on the MBED site. To
me, being able to use libraries is a great value, as is the MBED
paradigm, where so long as I can log on and plug in the board, I can
write code and test code. If I have to set up a GNU toolchain I'll
probably never get around to doing anything on it.
</pre>
</blockquote>
<br>
</body>
</html>