public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/93602] [9/10 Regression] Missing reference to libiconv in 9.x libstdc++ Date: Mon, 09 May 2022 16:35:38 +0000 [thread overview] Message-ID: <bug-93602-4-JWgIPUcx29@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93602-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93602 --- Comment #23 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:8da8ed881e7cdb2d4b070d685d6d3fe8d31529c2 commit r10-10601-g8da8ed881e7cdb2d4b070d685d6d3fe8d31529c2 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Apr 13 14:09:33 2022 +0100 libstdc++: Use LTLIBICONV when linking libstdc++.so [PR93602] This fixes missing libiconv symbols when libstdc++ is built on a system that has libiconv installed. If the libiconv headers are found then libstdc++ depends on libiconv_open etc instead of libc's iconv_open. But without this fix libstdc++ is not linked to the libiconv library that provides the definitions of those symbols. As discussed in PR 93602 this changed means that libstdc++.so.6 might have an rpath pointing to the location of the libiconv.so library. If that is not desired, then GCC must be configured to link to a static libiconv.a instead, using either --with-libiconv-type=static or an in-tree build of libiconv. libstdc++-v3/ChangeLog: PR libstdc++/93602 * doc/xml/manual/prerequisites.xml: Document libiconv workarounds. * doc/html/manual/setup.html: Regenerate. * src/Makefile.am (CXXLINK): Add $(LTLIBICONV). * src/Makefile.in: Regenerate. (cherry picked from commit c644b7df11afc818d6308c3776813e50e4ebe551)
next prev parent reply other threads:[~2022-05-09 16:35 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93602-4@http.gcc.gnu.org/bugzilla/> 2020-09-27 21:27 ` [Bug libstdc++/93602] " zvr+gcc at zvr dot gr 2020-12-07 12:44 ` [Bug libstdc++/93602] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-06-01 8:16 ` [Bug libstdc++/93602] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-04-12 20:36 ` redi at gcc dot gnu.org 2022-04-13 10:55 ` redi at gcc dot gnu.org 2022-04-13 14:37 ` redi at gcc dot gnu.org 2022-04-20 12:55 ` cvs-commit at gcc dot gnu.org 2022-04-20 12:57 ` [Bug libstdc++/93602] [9/10/11 " redi at gcc dot gnu.org 2022-04-21 12:32 ` cvs-commit at gcc dot gnu.org 2022-04-21 12:37 ` [Bug libstdc++/93602] [9/10 " redi at gcc dot gnu.org 2022-05-09 16:35 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-09 16:45 ` redi at gcc dot gnu.org 2022-05-27 8:42 ` [Bug libstdc++/93602] [9 " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-93602-4-JWgIPUcx29@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).