On 05/27/2015 08:54 AM, Richard Biener wrote:
On Wed, May 27, 2015 at 10:49 AM, Andreas Schwab wrote:
This breaks all checks for supported compiler options:
configure:6382: checking whether gcc supports -Wnarrowing
configure:6399: gcc -c -Wnarrowing conftest.c >&5
cc1: error: unrecognized com
On Wed, May 27, 2015 at 10:49 AM, Andreas Schwab wrote:
> This breaks all checks for supported compiler options:
>
> configure:6382: checking whether gcc supports -Wnarrowing
> configure:6399: gcc -c -Wnarrowing conftest.c >&5
> cc1: error: unrecognized command line option "-Wnarrowing"
> configu
This breaks all checks for supported compiler options:
configure:6382: checking whether gcc supports -Wnarrowing
configure:6399: gcc -c -Wnarrowing conftest.c >&5
cc1: error: unrecognized command line option "-Wnarrowing"
configure:6399: $? = 1
configure:6485: checking whether gcc supports -Wnar
On May 25, 2015, Alexandre Oliva wrote:
> I have one concern about scenarios in which config.cache is shared by
> all builds for the host, but in which stage1 and stage2 compilers might
> (and arguably should) get different results because of stage1's
> -std=c++98, but with a shared config.cache,
On May 22, 2015, Jason Merrill wrote:
> * configure.ac: Use C++ for all tests. Use AC_CHECK_DECLS for
> strstr and basename.
> * configure: Regenerate.
This is ok, thanks.
I have one concern about scenarios in which config.cache is shared by
all builds for the host, but in wh
My earlier patch to compile stage 1 with -std=c++98 ran into trouble on
FreeBSD, where that flag suppresses declaration of C99 library functions
like strtoull. I was surprised that configure was seeing the
declaration, but discovered that this was because configure was using
the C compiler rat
