From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't try building gdb against guile-2.2
Date: Sun, 08 Oct 2017 17:42:00 -0000 [thread overview]
Message-ID: <83vajpsfi6.fsf@gnu.org> (raw)
In-Reply-To: <ef9cc960416fc5d33fd59e139ff69c54@polymtl.ca> (message from Simon Marchi on Sun, 08 Oct 2017 13:20:28 -0400)
> Date: Sun, 08 Oct 2017 13:20:28 -0400
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Cc: gdb-patches@sourceware.org
>
> > 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).
Ah, okay. That's good enough, I think.
next prev parent reply other threads:[~2017-10-08 17:42 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
2017-10-08 17:42 ` Eli Zaretskii [this message]
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=83vajpsfi6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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