This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [patch] test-in-container: fix Arch Linux build-programs bug?
- From: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, DJ Delorie <dj at redhat dot com>, libc-alpha at sourceware dot org
- Date: Wed, 5 Sep 2018 18:30:23 +0200
- Subject: Re: [patch] test-in-container: fix Arch Linux build-programs bug?
- References: <xnzhx8cnzq.fsf@greed.delorie.com> <871f5a8b-7e90-47e7-f410-7f75b8fd2536@redhat.com> <20180831163436.68f72055@athena> <9d013c8b-d487-a144-5315-b99e6c05420a@redhat.com> <20180831185139.641fc194@athena> <alpine.DEB.2.21.1808311710340.3762@digraph.polyomino.org.uk> <20180903100925.63783162@athena> <71e876d1-81dc-0260-e117-e518182c472c@redhat.com> <20180905125033.78a8bc98@athena>
On Wed, 5 Sep 2018 12:52:36 +0200, Albert ARIBAUD
<albert.aribaud@3adev.fr> wrote :
> Now the question becomes: why is the build host native compiler used
> for links-dso-program.cc? Its only unique quality is to be C++, not C.
Just in case someone googling for the same type of issue reads this: DJ
pointed me to the cause and suggested a workaround (thanks you DJ!)
Apparently, the glibc configure process correctly guesses the C cross
compiler from host (and sets CC accordingly by itself it it was not set
already), but it might fail to guess the C++ cross compiler even though
it is present (and in the PATH), and it will then set CXX to g++. This
is what is happening in my case.
The workaround is to manually pre-set CXX=arm-linux-gnueabi-g++ and
export it (hence overriding any configure guesswork about the C++
compiler). If I do this, then the build failure disappears.
Cordialement,
Albert ARIBAUD
3ADEV