From: Doug Evans <dje@google.com>
To: guile-devel@gnu.org
Subject: Fwd: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6)
Date: Tue, 26 May 2020 10:57:45 -0700 [thread overview]
Message-ID: <CADPb22TpWCgDfxYVCBopYHes8fvG71k3nr334F+dRLNXq1V3jg@mail.gmail.com> (raw)
In-Reply-To: <bug-21104-4387-tiJKWgRHES@http.sourceware.org/bugzilla/>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Any takers?
---------- Forwarded message ---------
From: anatol.pomozov at gmail dot com <sourceware-bugzilla@sourceware.org>
Date: Tue, May 26, 2020 at 10:31 AM
Subject: [Bug guile/21104] 7.12.1 does not compile with latest guile (2.1.6)
To: <dje@google.com>
https://sourceware.org/bugzilla/show_bug.cgi?id=21104
--- Comment #16 from Anatol Pomozov <anatol.pomozov at gmail dot com> ---
This guile incompatibility issue still exists in the latest version of GDB.
GDB folks, do you have any estimation when this issue could be fixed?
--
You are receiving this mail because:
You are on the CC list for the bug.
[-- Attachment #2: Type: text/html, Size: 1124 bytes --]
parent reply other threads:[~2020-05-26 17:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-21104-4387-tiJKWgRHES@http.sourceware.org/bugzilla/>]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPb22TpWCgDfxYVCBopYHes8fvG71k3nr334F+dRLNXq1V3jg@mail.gmail.com \
--to=dje@google.com \
--cc=guile-devel@gnu.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).