From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: avr: freestanding libstdc++
Date: Mon, 20 Jul 2020 10:22:42 +0100 [thread overview]
Message-ID: <CAH6eHdRuoLVpSUyPpKv+2DFAUQkaXYFpGcm2SGeaokBmxV4Bnw@mail.gmail.com> (raw)
In-Reply-To: <rf1284$mto$1@ciao.gmane.io>
On Sun, 19 Jul 2020 at 10:04, Matwey V. Kornilov via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Hi,
>
> I am trying to build freestanding libstdc++ [1] for avr target in gcc
> 10.1. Initially, I wanted to play with coroutines, so I need <coroutine>.
>
> I use --enable-libstdcxx --disable-host-libstdcxx for configure.
>
> ./configure script runs fine with this arguments, but then make fails
> with the following:
>
> checking if /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 supports -fno-rtti
> -fno-exceptions... no
> checking for /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 option to produce PIC...
> -fPIC -DPIC
> checking if /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 PIC flag -fPIC -DPIC
> works... no
> checking if /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 static flag -static works... no
> checking if /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 supports -c -o file.o... yes
> checking if /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 supports -c -o file.o...
> (cached) yes
> checking whether the /home/matwey/temp/gcc-10.1.0/build/./gcc/xgcc
> -B/home/matwey/temp/gcc-10.1.0/build/./gcc/ -B/usr/avr/bin/
> -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
> --sysroot=/usr/avr/sys-root -mmcu=avrxmega3 linker
> (/home/matwey/temp/gcc-10.1.0/build/./gcc/collect-ld) supports shared
> libraries... yes
> checking whether -lc should be explicitly linked in... yes
> checking dynamic linker characteristics... no
> checking how to hardcode library paths into programs... immediate
> checking for shl_load... configure: error: Link tests are not allowed
> after GCC_NO_EXECUTABLES.
> make[1]: *** [Makefile:10635: configure-target-libstdc++-v3] Error 1
> make[1]: Leaving directory '/home/matwey/temp/gcc-10.1.0/build'
> make: *** [Makefile:954: all] Error 2
>
>
> Is it configuration supported for avr architecture?
I think it's not supported for avr. But I've been meaning to try it
for a few months and try to fix what fails, because I think it would
be really good to be able to use the freestanding parts of the C++
library for Arduino projects.
next prev parent reply other threads:[~2020-07-20 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 9:02 Matwey V. Kornilov
2020-07-20 9:22 ` Jonathan Wakely [this message]
2020-07-20 11:07 ` Matwey V. Kornilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH6eHdRuoLVpSUyPpKv+2DFAUQkaXYFpGcm2SGeaokBmxV4Bnw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=matwey.kornilov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).