From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, gdb-patches@sourceware.org,
Tom Tromey <tom@tromey.com>
Subject: Re: Commit: Sync top level configure and makefiles
Date: Wed, 10 Jan 2024 14:17:37 -0700 [thread overview]
Message-ID: <87mstc28i6.fsf@tromey.com> (raw)
In-Reply-To: <07b262c2-444f-49c6-a2b6-f2d4e40d4e2c@suse.de> (Tom de Vries's message of "Wed, 10 Jan 2024 16:49:53 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> This broke the gdb build for me on f39. I only have guile 3.0
Tom> installed, which is autodetected by the gdb build.
Sorry, I was under the impression that gdb's configure didn't look at
$GUILE.
Tom> But while double-checking guild in gdb/configure, it executes
Tom> /usr/bin/guild-3.0, which uses GUILE as set by the top-level makefile,
Tom> in other words, guile, which is not installed.
... I didn't realize this was going on. It seems very weird to me that
a versioned script like this is happy to accept any old interpreter and
not just hard-code the corresponding one.
Tom> I'd like to know if this is a user error or not.
No, I will try to fix it somehow. Maybe backing out my change is the
way to go.
Tom
prev parent reply other threads:[~2024-01-10 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 12:03 Nick Clifton
2024-01-10 15:49 ` Tom de Vries
2024-01-10 21:17 ` 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=87mstc28i6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
--cc=tdevries@suse.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).