From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't try building gdb against guile-2.2
Date: Sun, 08 Oct 2017 17:20:00 -0000 [thread overview]
Message-ID: <ef9cc960416fc5d33fd59e139ff69c54@polymtl.ca> (raw)
In-Reply-To: <83y3olsgty.fsf@gnu.org>
On 2017-10-08 13:13, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@polymtl.ca>
>> Cc: Simon Marchi <simon.marchi@polymtl.ca>
>> Date: Sun, 8 Oct 2017 12:47:03 -0400
>>
>> GDB currently doesn't build with Guile 2.2 (see PR 21104). If one has
>> both Guile 2.2 and 2.0 installed, GDB will pick up Guile 2.2 first and
>> fail building. Until somebody does the work of adapting the GDB code
>> to
>> Guile 2.2, we should not try using it. This patch therefore removes
>> it
>> from configure.
>>
>> gdb/ChangeLog:
>>
>> * configure.ac (try_guile_versions): Remove guile-2.2.
>> * configure: Regenerate.
>
> Should we perhaps have a configure-time option, by default off, to use
> Guile 2.2? Otherwise, how would that "somebody" work on fixing this
> problem, if they cannot even try building with Guile 2.2?
>
> Thanks.
They can pass --with-guile=guile-2.2. try_guile_versions, AFAIU,
contains the version to try by default if the version to use is not
explicitly passed (--with-guile or --with-guile=yes).
Simon
next prev parent reply other threads:[~2017-10-08 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 16:47 Simon Marchi
2017-10-08 17:14 ` Eli Zaretskii
2017-10-08 17:20 ` Simon Marchi [this message]
2017-10-08 17:42 ` Eli Zaretskii
2017-10-09 16:42 Doug Evans via gdb-patches
2017-10-09 16:52 ` Simon Marchi
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=ef9cc960416fc5d33fd59e139ff69c54@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@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