R0b0t1 kirjoitti 18.8.2017 klo 19:17:
On Fri, Aug 18, 2017 at 1:09 AM, Freddie Chopin wrote:
On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote:
On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote:
When compiling libssp, ssp.c, function __guard_setup:
O_RDONLY is undeclared (ssp.c:93:34),
ssize_t is
On Fri, 2017-08-18 at 11:17 -0500, R0b0t1 wrote:
> Just to check, this is actually an
> arm-none-eabi toolchain? I looked over the compilation flags and it
> looks like it supports all Cortex-M processor features like such a
> toolchain should. Most instructions I could find seemed to build a
> mor
On Fri, Aug 18, 2017 at 1:09 AM, Freddie Chopin wrote:
> On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote:
>> On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote:
>> > When compiling libssp, ssp.c, function __guard_setup:
>> > O_RDONLY is undeclared (ssp.c:93:34),
>> > ssize_t is an unknown type name (s
I forgot to say, that the procedure and resulting toolchain is closely
modeled after the one provided by ARM on:
https://developer.arm.com/open-source/gnu-toolchain/gnu-rm
It just has couple of tweaks like slightly different options for
newlib, completely disabled C++ exceptions and uses the most
On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote:
> On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote:
> > When compiling libssp, ssp.c, function __guard_setup:
> > O_RDONLY is undeclared (ssp.c:93:34),
> > ssize_t is an unknown type name (ssp.c:96:7), and
> > size_t is an unknown type name (ssp.c:113:
On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote:
> When compiling libssp, ssp.c, function __guard_setup:
> O_RDONLY is undeclared (ssp.c:93:34),
> ssize_t is an unknown type name (ssp.c:96:7), and
> size_t is an unknown type name (ssp.c:113:25).
>
> ../../src/gcc-7.2.0/configure --target=$TARGET --p
