This is the mail archive of the
mailing list for the GCC project.
Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers
- From: R0b0t1 <r030t1 at gmail dot com>
- To: GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 17 Aug 2017 22:27:16 -0500
- Subject: Re: C++ xgcc for arm-none-eabi fails in 7.1, 7.2 due to undefined identifiers
- Authentication-results: sourceware.org; auth=none
- References: <CAAD4mYh++6hLNi9_0ksmAL3kdoEiAZ6mT6+EH4RLggTqEY=1MQ@mail.gmail.com>
On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 <email@example.com> 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 --prefix=$PREFIX
> --with-cpu=cortex-m4 --with-fpu=fpv4-sp-d16 --with-float=hard
> --with-mode=thumb --enable-multilib --enable-interwork
> --enable-languages=c,c++ --with-system-zlib --with-newlib
> --disable-shared --disable-nls --with-gnu-as --with-gnu-ld
> A bootstrap C compiler is generated properly when passing --without-headers.
> I can provide more details and command output. Recently I was able to
> get 6.3.0 as close to working with Newlib 2.5 as I can tell, so this
> is not extremely urgent. Unfortunately I may have other questions
> about earlier GCC versions.
I attempted to reproduce my build of GCC 6.3 and it's no longer
working. Both builds on Kubuntu 17.04.
I'm kind of lost. Should I be filing bugs?
> Any suggestions related to generating cross toolchains, specifically
> generating a toolchain close to the one found at
> https://developer.arm.com/open-source/gnu-toolchain/gnu-rm, would be
> extremely helpful. Any help provided will be used to better support
> for generating toolchains with the crossdev project.
> I am very confused and what I want to do seems to be poorly documented.
> Thanks in advance,