From: Jeff Law <jeffreyalaw@gmail.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Pass GUILE down to subdirectories
Date: Sun, 31 Dec 2023 10:39:09 -0700 [thread overview]
Message-ID: <60ca2fe4-8a58-4e22-85e4-9a0a6a5e95b3@gmail.com> (raw)
In-Reply-To: <20231230212103.973170-1-tom@tromey.com>
On 12/30/23 14:21, Tom Tromey wrote:
> When I enable cgen rebuilding in the binutils-gdb tree, the default is
> to run cgen using 'guile'. However, on my host, guile is guile 2.2,
> which doesn't work for me -- I have to use guile3.0.
>
> This patch arranges to pass "GUILE" down to subdirectories, so I can
> use 'make GUILE=guile3.0'.
>
> ChangeLog
> 2023-12-30 Tom Tromey <tom@tromey.com>
>
> * Makefile.in: Rebuild.
> * Makefile.tpl (BASE_EXPORTS): Add GUILE.
> (GUILE): New variable.
> * Makefile.def (flags_to_pass): Add GUILE.
OK from the GCC side.
jeff
next prev parent reply other threads:[~2023-12-31 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 21:21 Tom Tromey
2023-12-31 17:39 ` Jeff Law [this message]
2024-01-13 11:35 ` Andrew Burgess
2024-01-15 3:05 ` Eric Gallager
2024-01-18 20:36 ` Tom Tromey
2024-01-21 17:39 ` Eric Gallager
2024-01-23 0:13 ` Tom Tromey
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=60ca2fe4-8a58-4e22-85e4-9a0a6a5e95b3@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).