This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH] Use a non-empty test program to test ability to link
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Sandra Loosemore <sandra at codesourcery dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Fri, 7 Feb 2020 22:24:21 +0000
- Subject: Re: [PATCH] Use a non-empty test program to test ability to link
- Ironport-sdr: zJsUjVLS2pnUc/mc9bTwsg+QLcIp0ooVWg5xWCVdgYORHcseo3nQHLW1Jl4UWFRFlzvpYTqO23 jELZ5fLXaQ/+xim/mLI3towsFsV+aeavf0eY5C164txnPCcRIjxNJW1ZoJ8KpgUUIlkt5uJ2qM MwQFPa4rBMHyrAgKhhA8rfT84Rf63GggU2FSaIavSvww/c05U48liY5Iq923dp/Sa67lmKWEJL QbknhZ6p48tRLD9ip54zkseLrQ47giDyY/H/6JJdxjTmNQ2yGRj/enxjn9dGEhIuKJfClrozoa w48=
- Ironport-sdr: jE/sGlcwGEXLOoLLZ0umBzbjZLMoMu0OuVNfiVg5aYBu7kyYQat9/pYCpXUxPi7vtTzevXgCUm mcVZwKMdF9rW+46coFtxXQ777czGGRt69Zck+d8JrcQ/kv2e9tGdwKw4F8FUT24J/2nX4dSQKj RN1aFFKO+w527x9rQDo6t1w0NzvtvbWMFsnztQ5afhbxjBIeCKtNwGT4y0iMKJz2REae6TPmIz ySofQyWwvqP/hBeToI4UOvvucc/tuIf+DgUt9DriwidDBKM9e9GKquuKGuTo1BhsBEP+ggbkaW 674=
- References: <e2e8405a-aede-7937-df79-83ded532d066@codesourcery.com>
On Wed, 5 Feb 2020, Sandra Loosemore wrote:
> This patch is for PR 79193 and 88999, problems where libstdc++ is
> mis-configuring itself when building for a bare-metal target because it thinks
> it can link programs without pulling in the BSP that provides low-level I/O
> support. (Specifically, this was observed on nios2-elf with Newlib and GDB
> semihosting.) It'll build just fine if it recognizes that it can only compile
> programs and not link them, but it's confused because using an empty program
> to test for ability to link succeeds.
>
> Is this configure change OK, and suitable for stage 4?
>
> BTW, I did run autoconf in every subdirectory that contains a configure.ac,
> but it appears only libstc++-v3 actually uses this test; all the other
> regenerated configure scripts were unchanged.
There's some problem with that regeneration, then; every directory where
configure.ac mentions GCC_NO_EXECUTABLES should have a resulting change (I
tested regenerating in libgcc/ with this patch applied and got such a
change, for example).
--
Joseph S. Myers
joseph@codesourcery.com