From: Yvan Roux <yvan.roux@linaro.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Alexandre Oliva <aoliva@redhat.com>, DJ Delorie <dj@redhat.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Paolo Bonzini <bonzini@gnu.org>
Subject: Re: [Libgomp, Fortran] Fix canadian cross build
Date: Thu, 05 Oct 2017 10:56:00 -0000 [thread overview]
Message-ID: <CAD57uCcAQiDQSmWZbKX9c_6Tz8v2uKsr2k+yUVsga7Zp1Mw8EA@mail.gmail.com> (raw)
In-Reply-To: <20170905100415.GE2323@tucnak>
On 5 September 2017 at 12:04, Jakub Jelinek <jakub@redhat.com> wrote:
> On Tue, Sep 05, 2017 at 10:58:22AM +0200, Yvan Roux wrote:
>> ping
>>
>> https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01784.html
>
> This really needs to be reviewed by a build machinery maintainer.
Thanks for the CC list update Jakub, ping again then...
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01784.html
>> >>>>> config/ChangeLog
>> >>>>> 2017-06-23 Yvan Roux <yvan.roux@linaro.org>
>> >>>>>
>> >>>>> * acx.m4 (NCN_STRICT_CHECK_TARGET_TOOLS): Renamed to ...
>> >>>>> (NCN_STRICT_PATH_TARGET_TOOLS): ... this. It reflects the replacement
>> >>>>> of AC_CHECK_PROG by AC_PATH_PROG to get the absolute name of the
>> >>>>> program.
>> >>>>> (ACX_CHECK_INSTALLED_TARGET_TOOL): Use renamed function.
>> >>>>>
>> >>>>> ChangeLog
>> >>>>> 2017-06-23 Yvan Roux <yvan.roux@linaro.org>
>> >>>>>
>> >>>>> * configure.ac: Use NCN_STRICT_PATH_TARGET_TOOLS instead of
>> >>>>> NCN_STRICT_CHECK_TARGET_TOOLS.
>> >>>>> * configure: Regenerate.
>
> Jakub
next prev parent reply other threads:[~2017-10-05 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 13:44 Yvan Roux
2017-07-03 9:21 ` Yvan Roux
2017-07-11 10:25 ` Yvan Roux
2017-08-04 13:52 ` Yvan Roux
2017-08-18 9:31 ` Yvan Roux
2017-09-05 8:58 ` Yvan Roux
2017-09-05 10:04 ` Jakub Jelinek
2017-10-05 10:56 ` Yvan Roux [this message]
2017-10-05 11:39 ` Petr Ovtchenkov
2018-02-01 11:33 ` Yvan Roux
2018-05-23 9:07 ` Maxim Kuvyrkov
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=CAD57uCcAQiDQSmWZbKX9c_6Tz8v2uKsr2k+yUVsga7Zp1Mw8EA@mail.gmail.com \
--to=yvan.roux@linaro.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).