This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
- From: Kai Ruottu <kai dot ruottu at wippies dot com>
- To: "onkel dot jack at t-online dot de" <onkel dot jack at t-online dot de>, "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Thu, 31 Mar 2016 01:58:20 +0300
- Subject: Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
- Authentication-results: sourceware.org; auth=none
- References: <1459342340242 dot 909508 dot 3fb8ceeaf05f65d7b223e142969681ed18c43fd4 at spica dot telekom dot de>
30.3.2016, 15:52, onkel.jack@t-online.de kirjoitti:
Trying to build a cross tool chain under mingw64 or cygwin64 I run into the problem:
configure: error: No support for this host/target combination. at building libstdc++-v3.
configure options are:
binutils 2.4 : --target=arm-none-eabi --prefix=/opt/arm-none-eabi-5.3.0 --disable-nls --disable-werror
gcc-boot 5.3.0 : --target0arm-none-eabi --prefix=/opt/arm-none-eabi-5.3.0 \
--with-newlib=../$(NEWLIB) --with-gnu-as --with-gnu-ld
Please explain what this "--with-newlib=../$(NEWLIB)" should do, the GCC
install docs don't know it...
Seemingly you are trying to use the Cygwin extensions for newlib with
'arm-eabi'. Has this some sanity?
The "--with-gnu-as --with-gnu-ld" then are vain in an embedded target
case - no "native" or other
alternatives...
--disable-nls --disable-libssp \
--disable-gomp --disable-libstcxx-pch --enable-multilib --enable-threads \
The "--enable-threads" could also need some explanation, what "threads"
you are expecting with the
'arm-eabi' embedded target?
--disable-shared --enable-static \
--disable-libmudflap --enable-interwork --enable-languages=c,c++
Just for curiousness I tried a gcc-5.3.0 with newlib-2.4.0 build for
'arm-eabi' target on Linux. With bare
'--with-newlib' and with '--disable-threads'. Also first disabling
multilib and interwork, just wanting to
see whether the libstdc++-v3 configure will succeed... No problems in
configure, neither in libstdc++-v3
build for 'arm-eabi'. Let's see what happens after enabling multilib and
interwork - leaving it for the night...