From: Jeff Law <law@redhat.com>
To: Michael Darling <darlingm@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fixes combined gcc-binutils builds.
Date: Wed, 27 May 2015 15:52:00 -0000 [thread overview]
Message-ID: <5565E433.2060006@redhat.com> (raw)
In-Reply-To: <CABRuA+h2f3u=QdawpM=wcfyTmGaAm4YzM6GyxYcD9ysnoUaeFg@mail.gmail.com>
On 05/24/2015 01:56 PM, Michael Darling wrote:
> Combined builds has been broken for about 10 months, because some
> binutils configure.in files were renamed to configure.ac, but gcc's
> references to them were not updated. There is a corresponding patch
> submitted to binutils-gdb, which renames its few remaining configure.in
> files to configure.ac. Otherwise, fixing the gcc calls to binutils-gdb
> configure.* files would be more complicated.
>
> Also, some time ago, gcc renamed its configure.in files to configure.ac.
> Fixed a few remaining references to gcc configure.in files, such as in
> error messages and documentation.
Can you please send your patch as an attachment. Your mailer re-wrapped
the long lines making the patch impossible to apply and test.
Jeff
next prev parent reply other threads:[~2015-05-27 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 0:56 Michael Darling
2015-05-27 15:52 ` Jeff Law [this message]
2015-07-17 0:47 ` Michael Darling
2015-07-24 18:35 ` Jeff Law
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=5565E433.2060006@redhat.com \
--to=law@redhat.com \
--cc=darlingm@gmail.com \
--cc=gcc-patches@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).