From: Paolo Bonzini <bonzini@gnu.org>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Tom Tromey <tromey@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v4 04/20] add configury
Date: Mon, 30 Sep 2013 09:26:00 -0000 [thread overview]
Message-ID: <52492C0A.4030505@gnu.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1309272239160.2211@trevally.site>
Il 27/09/2013 21:45, Gerald Pfeifer ha scritto:
> I believe this may be breaking all my testers on FreeBSD
> (i386-unknown-freebsd10.0 for example). The timing of when this
> patchset went in fits pretty much when my builds started to break
> and I am wondering about some code.
>
> Here is the failure mode:
>
> gmake[2]: Entering directory `/scratch/tmp/gerald/OBJ-0927-1848/gcc'
> g++ -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -fno-exceptions -fno-rtti
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
> -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common
> -DHAVE_CONFIG_H -I. -Ic -I/scratch/tmp/gerald/gcc-HEAD/gcc ...[-I
> options]...
> -o c/c-lang.o -MT c/c-lang.o -MMD -MP -MF c/.deps/c-lang.TPo
> /scratch/tmp/gerald/gcc-HEAD/gcc/c/c-lang.c
> cc1plus: error: unrecognized command line option "-Wno-narrowing"
> gmake[2]: *** [c/c-lang.o] Error 1
> gmake[1]: *** [install-gcc] Error 2
> gmake: *** [install] Error 2
>
> The issue is the invocation of g++ (the old system compiler, not what
> we built) with -Wno-narrowing (a new option).
Why is install building anything?
Paolo
next prev parent reply other threads:[~2013-09-30 7:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 14:12 [PATCH v4 00/20] resurrect automatic dependencies Tom Tromey
2013-09-23 14:12 ` [PATCH v4 04/20] add configury Tom Tromey
2013-09-27 20:10 ` Gerald Pfeifer
2013-09-27 21:57 ` Tom Tromey
2013-09-30 9:26 ` Paolo Bonzini [this message]
2013-09-30 16:08 ` Iain Sandoe
2013-10-14 22:53 ` Gerald Pfeifer
2013-10-15 7:57 ` Paolo Bonzini
2013-10-15 13:34 ` Tom Tromey
2013-10-16 0:21 ` Gerald Pfeifer
2013-10-16 21:01 ` Tom Tromey
2013-09-23 14:12 ` [PATCH v4 08/20] convert the ObjC front end to automatic dependencies Tom Tromey
2013-09-23 17:16 ` Mike Stump
2013-09-23 14:12 ` [PATCH v4 11/20] Fix up c-family targets Tom Tromey
2013-09-23 14:12 ` [PATCH v4 16/20] make out_object_file rule use automatic dependencies Tom Tromey
2013-09-23 14:12 ` [PATCH v4 17/20] fix t-i386 Tom Tromey
2013-09-23 14:12 ` [PATCH v4 07/20] convert the C++ front end to automatic dependencies Tom Tromey
2013-09-23 14:12 ` [PATCH v4 15/20] remove explicit dependencies Tom Tromey
2021-08-09 11:34 ` Thomas Schwinge
2013-09-23 14:12 ` [PATCH v4 01/20] clean up SHLIB so subshells are not needed Tom Tromey
2013-09-23 14:12 ` [PATCH v4 18/20] fix t-glibc Tom Tromey
2013-09-23 14:12 ` [PATCH v4 02/20] update generated_files Tom Tromey
2013-09-23 14:12 ` [PATCH v4 03/20] move generated_files order-only dependency later Tom Tromey
2013-09-23 14:12 ` [PATCH v4 12/20] convert the Fortran front end to automatic dependencies Tom Tromey
2013-09-23 19:24 ` Tobias Burnus
2013-09-23 14:31 ` [PATCH v4 09/20] convert the ObjC++ " Tom Tromey
2013-09-23 17:43 ` Mike Stump
2013-09-23 14:31 ` [PATCH v4 10/20] convert the Java " Tom Tromey
2013-09-23 14:31 ` [PATCH v4 06/20] convert the C " Tom Tromey
2013-09-23 14:32 ` [PATCH v4 05/20] remove AM_PROG_CC_C_O Tom Tromey
2013-09-23 14:45 ` [PATCH v4 13/20] convert the Go front end to automatic dependencies Tom Tromey
2013-09-23 14:48 ` [PATCH v4 20/20] remove unused macros Tom Tromey
2013-09-23 14:53 ` [PATCH v4 14/20] convert LTO to automatic dependencies Tom Tromey
2013-09-23 14:54 ` [PATCH v4 19/20] remove last definition of CROSS_FLOAT_H Tom Tromey
2013-09-25 8:07 ` [PATCH v4 00/20] resurrect automatic dependencies Alexandre Oliva
2013-09-25 8:39 ` Paolo Bonzini
2013-09-25 17:19 ` Tom Tromey
2013-09-25 17:34 ` Jan Hubicka
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=52492C0A.4030505@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=tromey@redhat.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).