This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ToT build failure?
- From: David Malcolm <dmalcolm at redhat dot com>
- To: sellcey at cavium dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 06 Jul 2017 13:18:04 -0400
- Subject: Re: ToT build failure?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dmalcolm at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 345C1C04B927
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 345C1C04B927
- References: <201707061705.v66H5Jv5002389@sellcey-dt.caveonetworks.com>
On Thu, 2017-07-06 at 10:05 -0700, Steve Ellcey wrote:
> Is anyone else having problems building a cross-gcc where an intial
> gcc with C only is built first and used to build glibc? I am
> trying this (it worked before) and am getting:
>
> /local/sellcey/gcc-aarch64/obj/gcc_initial/./gcc/xgcc
> -B/local/sellcey/gcc-aarch64/obj/gcc_initial/./gcc/ -xc++ -nostdinc
> /dev/null -S -o /dev/null -fself-test=/local/sellcey/gcc
> -aarch64/src/gcc/gcc/testsuite/selftests
> xgcc: error: language c++ not recognized
> xgcc: error: language c++ not recognized
> Makefile:1972: recipe for target 's-selftest-c++' failed
> make[1]: *** [s-selftest-c++] Error 1
>
> The configure I use to build the initial GCC is:
>
> /local/sellcey/gcc-aarch64/src/gcc/configure -
> -prefix=/local/sellcey/gcc-aarch64/install --target=aarch64-cross
> -linux-gnu --with-newlib --without-headers --with
> -sysroot=/local/sellcey/gcc-aarch64/install --enable-languages=c -
> -enable-threads=no --disable-shared --disable-decimal-float --disable
> -libsanitizer --disable-bootstrap
>
> This is an x86 to aarch64 cross compiler.
>
> Steve Ellcey
> sellcey@cavium.com
This is due to r250030, in which I added C++-specific selftests; looks
like I need to also conditionalize them on --enable-languages.
Sorry about this.
A workaround is presumably to:
touch s-selftest-c++
I'll revert that change shortly.
Dave