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: Zack Weinberg <zackw at panix dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: Steve Ellcey <sellcey at cavium dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 24 Sep 2018 16:26:46 -0400
- Subject: Re: Bootstrap build problem after V8 test-in-container patch".
- References: <CAKCAbMgFom5KH05gk-w_BLE_-MMCwDGM-df-ztqi_ky75OtN=Q@mail.gmail.com> <xnftxylk55.fsf@greed.delorie.com>
On Mon, Sep 24, 2018 at 4:23 PM DJ Delorie <dj@redhat.com> wrote:
> Zack Weinberg <zackw@panix.com> writes:
>
> > This sounds like a job for automake's "missing" script.
>
> Heh, the problem happens when it's user-specified but *not* missing,
> just the wrong one.
What I meant was, if you know you have arm-linux-gcc but not
arm-linux-g++, you could explicitly set CXX='${srcdir}/missing g++'
and I _think_ that would get you a nice clear error iff the build
actually tries to use the C++ compiler.
zw