From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Pass GUILE down to subdirectories
Date: Thu, 18 Jan 2024 13:36:06 -0700 [thread overview]
Message-ID: <87a5p2xtu1.fsf@tromey.com> (raw)
In-Reply-To: <87edel79f6.fsf@redhat.com> (Andrew Burgess's message of "Sat, 13 Jan 2024 11:35:41 +0000")
Andrew> This change is causing some problems for me.
Yeah, Tom de Vries as well.
Andrew> One of my build machines has 2 versions of guile installed. One is
Andrew> guile 2.0.14 and the other is guile 2.2.21.
Andrew> When GDB configures itself the configure script figures out that it
Andrew> should use 2.2.21 to compile the guile libraries that GDB uses.
Andrew> However, when we actually build the guile libraries we do use guild2.2,
Andrew> but due to this 'GUILE = guile' line, guild2.2 uses guile 2.0.14 in
Andrew> order to perform the compile (I guess, I don't know the details of how
Andrew> guile compilation works).
Andrew> Unfortunately guile 2.0.14 compiles in a way which is not compatible
Andrew> with how GDB then tries to load the guile library.
I consider this a bug in guile -- it installs 'guild' with this:
#!/usr/bin/sh
# -*- scheme -*-
exec ${GUILE:-/usr/bin/guile2.2} $GUILE_FLAGS -e '(@@ (guild) main)' -s "$0" "$@"
!#
Allowing a system script to pick $GUILE here seems weird, especially for
a versioned install of "guild", where as you can see it already knows
the correct guile to use.
However -- I think it's better to just work around this.
I plan to back out this change. Anyone needing to re-run cgen (which
itself ought to come with smarts here, but since it is un-maintained...)
can just specify this by hand. I.e., the status quo ante.
I'll try to send a patch tomorrow.
Tom
next prev parent reply other threads:[~2024-01-18 20:36 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 [this message]
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=87a5p2xtu1.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--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).