From: DJ Delorie <dj@redhat.com>
To: Yaakov Selkowitz <yselkowi@redhat.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: [PATCH] toplevel: fixes for in-tree libiconv
Date: Tue, 16 Jun 2015 04:09:00 -0000 [thread overview]
Message-ID: <201506160408.t5G48wwJ024192@greed.delorie.com> (raw)
In-Reply-To: <1432934043.7892.30.camel@redhat.com> (message from Yaakov Selkowitz on Fri, 29 May 2015 16:14:03 -0500)
> This is the first in a series of patches to make a build with an in-tree
> GNU libiconv work as designed.
>
> This patch fixes dependencies for parallel make, and avoids failures
> with make targets not supported by GNU libiconv.
This is OK. Thanks!
next prev parent reply other threads:[~2015-06-16 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 21:14 Yaakov Selkowitz
2015-05-30 4:50 ` Jeff Law
2015-06-16 4:09 ` DJ Delorie [this message]
2015-06-18 22:48 ` Yaakov Selkowitz
2015-06-19 6:31 ` DJ Delorie
2015-07-01 20:43 ` Yaakov Selkowitz
2015-08-07 5:15 ` DJ Delorie
2015-07-01 20:45 ` Yaakov Selkowitz
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=201506160408.t5G48wwJ024192@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yselkowi@redhat.com \
/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