From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-468047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 17807 invoked by alias); 22 Nov 2014 10:52:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 17757 invoked by uid 48); 22 Nov 2014 10:52:30 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64023] [5 Regression] r216964 breaks bootstrap on darwin when using gcc as the bootstrap compiler.
Date: Sat, 22 Nov 2014 10:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64023-4-9U2I5vMXfs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64023-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64023-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg02519.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64023

--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> ---
as commented in 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63773 c#14..17
this is caused by
$(HOST_EXPORTS) being used at stage#N>1 instead of $(POSTSTAGE1_HOST_EXPORTS)

Thus the config test for the bootstrap compiler is affecting the later build. 
In this case, GCC fails to build because it supports -static-libstdc++ (and
thus the option is passed to the build) but it then needs the -B options to
allow for spec substitution to work for libstdc++.  These are not present in
HOST_EXPORTS because, obviously, the host compiler is installed and doesn't
need them.

NOTE: (clang succeeds because it does not support -staticlibstdc++, so that
option is not passed to the stage#3 libs build.
However in that case the fault is potentially more subtle, because the library
is then being linked with a dependency on the *system* libstdc++.dylib and not
the current build.