This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Bootstrap build problem after V8 test-in-container patch".
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Steve Ellcey <sellcey at cavium dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, DJ Delorie <dj at redhat dot com>
- Date: Thu, 23 Aug 2018 20:02:36 +0000
- Subject: Re: Bootstrap build problem after V8 test-in-container patch".
- References: <1535048185.20144.18.camel@cavium.com>
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