From: Yaakov Selkowitz <yselkowi@redhat.com>
To: gcc-patches@gcc.gnu.org,
"binutils@sourceware.org" <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PATCH] config: fix AM_ICONV for in-tree libiconv
Date: Fri, 29 May 2015 21:25:00 -0000 [thread overview]
Message-ID: <1432934749.13692.9.camel@redhat.com> (raw)
This is the second in a series of patches to make a build with an
in-tree GNU libiconv work as designed.
Currently GDB is the only toolchain component which actually uses an
in-tree libiconv. This patch modifies the common AM_ICONV to use an
in-tree libiconv when present and not already provided by libc. (GDB's
workaround uses an in-tree libiconv even when libc provides iconv(3);
I'm not sure when or why that would be desirable.)
Once these two patches are merged in to each tree, I will follow with
patches to regenerate the various configure scripts and a few other
minor corresponding changes.
--
Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.
next reply other threads:[~2015-05-29 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 21:25 Yaakov Selkowitz [this message]
2015-07-01 20:46 ` Yaakov Selkowitz
2015-07-01 20:52 ` Yaakov Selkowitz
2015-07-01 20:53 ` Yaakov Selkowitz
2015-07-01 22:13 ` Yaakov Selkowitz
2015-08-22 17:05 ` Pedro Alves
2015-08-23 19:37 ` Yaakov Selkowitz
2015-08-24 10:29 ` Pedro Alves
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=1432934749.13692.9.camel@redhat.com \
--to=yselkowi@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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).