From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] Simplify definition of GUILE
Date: Sat, 26 Aug 2023 13:09:29 -0600 [thread overview]
Message-ID: <87o7ittyc6.fsf@tromey.com> (raw)
In-Reply-To: <20230822194804.1306194-1-tom@tromey.com> (Tom Tromey's message of "Tue, 22 Aug 2023 13:48:04 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This patch sets GUILE to just plain 'guile'.
Tom> In the distant ("devo") past, the top-level build did support building
Tom> Guile in-tree. However, I don't think this really works any more.
Tom> For one thing, there are no build dependencies on it, so there's no
Tom> guarantee it would actually be built before the uses.
Tom> This patch also removes the use of "-s" as an option to cgen scheme
Tom> scripts. With my latest patch upstream, this is no longer needed.
Tom> After the upstream changes, either Guile 2 or Guile 3 will work, with
Tom> or without the compiler enabled.
Alan OK'd the opcodes part of this, so I wrote a ChangeLog entry for
that, and I'm going to push the whole patch now.
To recap the current state -- cgen works with guile 2 and guile 3 now.
You can use the guile compiler, which speeds things up quite a bit; just
ignore all the warnings.
Tom
prev parent reply other threads:[~2023-08-26 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 19:48 Tom Tromey
2023-08-26 19:09 ` Tom Tromey [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=87o7ittyc6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.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).