From: Tom Tromey <tom@tromey.com>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: Tom Tromey <tom@tromey.com>,
Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Pass GUILE down to subdirectories
Date: Mon, 22 Jan 2024 17:13:15 -0700 [thread overview]
Message-ID: <87h6j4sy90.fsf@tromey.com> (raw)
In-Reply-To: <CAMfHzOufGr=Y1xUZ820ws=CBBzqTT0G5u2LQ+PHCu3hQoKsXgQ@mail.gmail.com> (Eric Gallager's message of "Sun, 21 Jan 2024 12:39:38 -0500")
Eric> I mean, I've been trying to figure out how to re-run cgen myself, to
Eric> regenerate some cgen-erated files in libopcodes to fix some compiler
Eric> warnings in them, but it's pretty hard to do so; I'd really appreciate
Eric> it if the whole process of regenerating files with cgen could be made
Eric> easy and well-documented and understandable...
Yeah. Unfortunately cgen seems fairly unmaintained and guile still
seems a bit clunky to use somehow (or maybe it's packaged strangely, I
don't know).
After some patches of mine to let cgen use the guile compiler, it
requires guile 3.0 (at least for me, guile 2 dies while trying to run
it). So what I do is:
* cd binutils-gdb
* ln -s /path/to/cgen
* configure a new directory with --enable-cgen-maint
* make GUILE=guile3.0
Tom
prev parent reply other threads:[~2024-01-23 0:13 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
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 [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=87h6j4sy90.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.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).