From: Alexandre Oliva <oliva@gnu.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] contrib: Fill in HOST{CC,CFLAGS,CXX,CXXFLAGS} in test_installed
Date: Tue, 06 Feb 2024 02:12:37 -0300 [thread overview]
Message-ID: <oro7cu6ure.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <ZcDnilo9xkjaDa/u@tucnak> (Jakub Jelinek's message of "Mon, 5 Feb 2024 14:50:02 +0100")
On Feb 5, 2024, Jakub Jelinek <jakub@redhat.com> wrote:
> * test_installed: Fill in HOSTCC, HOSTCXX, HOSTCFLAGS and
> HOSTCXXFLAGS.
LGTM, thanks,
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice but
very few check the facts. Think Assange & Stallman. The empires strike back
prev parent reply other threads:[~2024-02-06 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 13:50 Jakub Jelinek
2024-02-05 16:07 ` Jeff Law
2024-02-06 5:12 ` Alexandre Oliva [this message]
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=oro7cu6ure.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.de \
/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).