[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 sandra at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from sandra at gcc dot gnu.org --- I think I just forgot to close this issue at the time I committed the patch. Ooops!
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 --- Comment #7 from Jonathan Wakely --- Sandra, does the commit above fix this? You mentioned it not being fully general, but is it good enough?
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 --- Comment #6 from CVS Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:02ce382cd323097f9d02fbf91e0a3f59ebcd3d30 commit r10-6603-g02ce382cd323097f9d02fbf91e0a3f59ebcd3d30 Author: Sandra Loosemore Date: Wed Feb 12 12:20:15 2020 -0800 Use a non-empty test program to test ability to link. On bare-metal targets, I/O support is typically provided by a BSP and requires a linker script and/or hosting library to be specified on the linker command line. Linking an empty program with the default linker script may succeed, however, which confuses libstdc++ configuration when programs that probe for the presence of various I/O features fail with link errors. 2020-02-12 Sandra Loosemore PR libstdc++/79193 PR libstdc++/88999 config/ * no-executables.m4: Use a non-empty program to test for linker support. libgcc/ * configure: Regenerated. libgfortran/ * configure: Regenerated. libiberty/ * configure: Regenerated. libitm/ * configure: Regenerated. libobjc/ * configure: Regenerated. libquadmath/ * configure: Regenerated. libssp/ * configure: Regenerated. libstdc++v-3/ * configure: Regenerated.
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 --- Comment #5 from sandra at gcc dot gnu.org --- *** Bug 88999 has been marked as a duplicate of this bug. ***
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 --- Comment #4 from Jonathan Wakely --- This seems reasonable to me, but this area of the configury is not my forte.
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 --- Comment #3 from sandra at gcc dot gnu.org --- Created attachment 40649 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40649=edit patch to use "hello, world" to test linking The attached patch is sufficient to cause a link failure in cases where a linker script or additional library options are required to support stdio.h features. This might not be fully general since other C99 feature checks assume that math.h, complex.h, stdlib.h, and wchar.h features don't require any special linker recipe either.
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 sandra at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |NEW --- Comment #2 from sandra at gcc dot gnu.org --- What is "it" that I'm supposed to change? Note that things are going wrong in the libstdc++-v3/configure script well before this comment (which appears at line 21812). The initial empty-program link test is at line 3972. The link test for checking C99 stdio.h support is at line 16961.
[Bug libstdc++/79193] libstdc++ configure incorrectly decides linking works for cross-compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79193 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2017-01-23 Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski --- # Only do link tests if native. Else, hardcode. So if hardcode is not correct for your target (newlib or otherwise). Then you need to change it
