Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi

["onkel dot jack at t-online dot de" <onkel dot jack at t-online dot de>]

--with-newlib= I took from a older recipie I had used for build gcc4.7, but youre right, doc does not say it has a arg
don't know where i originally got that from.

newlib-cygwin is not for Cygwin extensions, its just the repository name if you do a git clone from sourceware.org, the original newlib source. Had to use it since newlib-2.3.0 is broken for arm. (2.4.0 just got released, I use it now)

--enable-threads I would like to have to have thread safe stuff later on, my operating system provide them (to be integrated )
  for now --enable-threads w/o an arg means single, this is no threads

--enable-interwork I may omit at all, I don't believe I really want to use mixed mode 
but --enable-multilib is essentiell.


-----Original-Nachricht-----
Betreff: Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
Datum: 2016-03-31T00:59:43+0200
Von: "Kai Ruottu" <kai.ruottu@wippies.com>
An: "onkel.jack@t-online.de" <onkel.jack@t-online.de>, "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>

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...