From: Alan Modra <amodra@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Alan Modra via Gdb-patches <gdb-patches@sourceware.org>,
binutils@sourceware.org, aburgess@redhat.com, vapier@gentoo.org
Subject: Re: sim --enable-cgen-maint
Date: Fri, 11 Aug 2023 08:49:00 +0930 [thread overview]
Message-ID: <ZNVwZD2twQNGXtdl@squeak.grove.modra.org> (raw)
In-Reply-To: <875y5m3k5x.fsf@tromey.com>
On Thu, Aug 10, 2023 at 11:02:34AM -0600, Tom Tromey wrote:
> >>>>> "Alan" == Alan Modra via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Alan> Fix that by making both use ../cgen first, then ../../cgen
> Alan> relative to sim/ and opcodes/.
>
> Are there other tools that can be installed parallel to the top-level
> source directory? I am pretty surprised to see that at all, since I
> think the "normal" approach to this kind of thing is to work with the
> uberbaum setup; and otherwise to look for tools on PATH.
We're looking for the cgen source, git://sourceware.org/git/cgen.git.
That's likely not on $PATH. Yes, likely the best place to find it is
the uberbaum setup, ie. when you git clone both cgen.git and
binutils-gdb.git from the same place. That's the location assumed by
the sim sources currently. However, binutils-gdb currently assumes
cgen.git is cloned *inside* the binutils-gdb source or that you've set
up a symbolic link there to wherever the source is located.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2023-08-10 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 6:13 Alan Modra
2023-08-10 17:02 ` Tom Tromey
2023-08-10 23:19 ` Alan Modra [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=ZNVwZD2twQNGXtdl@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=vapier@gentoo.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).