public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zvr+gcc at zvr dot gr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93602] Missing reference to libiconv in 9.x libstdc++
Date: Sun, 27 Sep 2020 21:27:20 +0000 [thread overview]
Message-ID: <bug-93602-4-oIry9OWucr@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
Alexios Zavras (zvr) <zvr+gcc at zvr dot gr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zvr+gcc at zvr dot gr
--- Comment #14 from Alexios Zavras (zvr) <zvr+gcc at zvr dot gr> ---
I can confirm this bug also in gcc-9.3.0, gcc-10.1.0 and gcc-10.2.0.
To recap: if the system has a libiconv installed, the generated and installed
libstdc++.so depends on it.
However the compiler, when using it when compiling a C++ program, does not link
libiconv, resulting in an error:
$ g++ foo.cc
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib64/libstdc++.so:
undefined reference to `libiconv'
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib64/libstdc++.so:
undefined reference to `libiconv_close'
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
/usr/local/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib64/libstdc++.so:
undefined reference to `libiconv_open'
collect2: error: ld returned 1 exit status
next parent reply other threads:[~2020-09-27 21:27 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 ` zvr+gcc at zvr dot gr [this message]
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
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-oIry9OWucr@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: link
Be 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).