From: Jeff Law <law@redhat.com>
To: Olivier Hainque <hainque@adacore.com>, gcc-patches@gcc.gnu.org
Cc: Nicolas Roche <roche@adacore.com>
Subject: Re: [patch] propagate INSTALL Makefile variables down from gcc/
Date: Sat, 30 Aug 2014 06:36:00 -0000 [thread overview]
Message-ID: <540170D7.4060804@redhat.com> (raw)
In-Reply-To: <A32C1082-F2CD-4596-B76B-E02B6C1DA135@adacore.com>
On 08/21/14 09:49, Olivier Hainque wrote:
> Hello,
>
> Experiments with custom install programs exposed that the INSTALL series of
> Makefile variables aren't propagated down from the gcc subdir.
>
> This patch fixes this. Checked that it addressed the unexpected behavior we
> were observing + bootstrapped & regtested on x86_64-linux-gnu.
>
> OK to commit ?
>
> Thanks in advance for your feedback,
>
> With Kind Regards,
>
> Olivier
>
>
> 2014-08-21 Nicolas Roche <roche@adacore.com>
>
> * Makefile.in (FLAGS_TO_PASS): Propagate INSTALL, INSTALL_DATA,
> INSTALL_SCRIPT and INSTALL_PROGRAM as well.
OK.
Jeff
next prev parent reply other threads:[~2014-08-30 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 15:50 Olivier Hainque
2014-08-30 6:36 ` Jeff Law [this message]
2014-09-01 8:44 ` Olivier Hainque
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=540170D7.4060804@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=roche@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).