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: Joseph Myers <joseph at codesourcery dot com>
- To: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>
- Cc: Carlos O'Donell <carlos at redhat dot com>, DJ Delorie <dj at redhat dot com>, <libc-alpha at sourceware dot org>
- Date: Wed, 5 Sep 2018 16:49:45 +0000
- 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> <20180905183023.7cf1846c@athena>
On Wed, 5 Sep 2018, Albert ARIBAUD wrote:
> 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.
Exporting the variables in the environment is another obsolescent practice
(setting them on the configure command line, as arguments to configure, is
preferred for configure scripts generated with autoconf 2.50 or later).
(See NEWS for autoconf 2.50, released in 2001.)
--
Joseph S. Myers
joseph@codesourcery.com