public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: Commit: Sync top level configure and makefiles
Date: Wed, 10 Jan 2024 16:49:53 +0100	[thread overview]
Message-ID: <07b262c2-444f-49c6-a2b6-f2d4e40d4e2c@suse.de> (raw)
In-Reply-To: <87wmsh5r9u.fsf@redhat.com>

On 1/10/24 13:03, Nick Clifton wrote:
> commit b7e5a29602143b53267efcd9c8d5ecc78cd5a62f
> Author: Tom Tromey<tom@tromey.com>
> Date:   Tue Jan 9 06:25:26 2024 -0700
> 
>      Pass GUILE down to subdirectories
>      
>      When I enable cgen rebuilding in the binutils-gdb tree, the default is
>      to run cgen using 'guile'.  However, on my host, guile is guile 2.2,
>      which doesn't work for me -- I have to use guile3.0.
>      
>      This patch arranges to pass "GUILE" down to subdirectories, so I can
>      use 'make GUILE=guile3.0'.
>      

This broke the gdb build for me on f39.  I only have guile 3.0 
installed, which is autodetected by the gdb build.

But while double-checking guild in gdb/configure, it executes 
/usr/bin/guild-3.0, which uses GUILE as set by the top-level makefile, 
in other words, guile, which is not installed.

Presumable passing down GUILE=/usr/bin/guile-3.0 or some such will fix 
this, I haven't tried yet.

I'd like to know if this is a user error or not.

Thanks,
- Tom


  reply	other threads:[~2024-01-10 15:49 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 [this message]
2024-01-10 21:17   ` 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=07b262c2-444f-49c6-a2b6-f2d4e40d4e2c@suse.de \
    --to=tdevries@suse.de \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=tom@tromey.com \
    /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).