Bootstrap build problem after V8 test-in-container patch".

[Joseph Myers]

On Thu, 23 Aug 2018, Steve Ellcey wrote:

> I am having a build problem after DJ's patch "V8 test-in-container patch".
> 
> I do a bootstrap build by building binutils, then I build a 'partial gcc'
> by building "all-gcc all-target-libgcc" and
> "install-gcc install-target-libgcc", then I build glibc using that gcc,
> followed by a complete build of gcc.

The expectation is that the first compiler in a bootstrap build is 
static-only and C-only.  Presumably yours supports C++ as well, enough for

ifeq (,$(CXX))

to fail and so end up trying to link with -lstdc++ -lgcc_s?

Ideally it *would* be possible to build the host side of a full 
multi-language GCC with static-only libgcc, then later build all the 
target libraries including rebuilding libgcc (rather than needing to build 
the host side twice to get it properly configured for shared libraries), 
so one might hope that $(CXX) existing would not by itself cause attempts 
to link with -lstdc++ at glibc build time (as opposed to at *testsuite* 
build time).

-- 
Joseph S. Myers
joseph@codesourcery.com