unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guile-user@gnu.org, Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Subject: Re: How to build GNUTLS Guile bindings on Xubuntu
Date: Sat, 17 Nov 2018 16:34:07 -0500	[thread overview]
Message-ID: <87lg5rwfpx.fsf@netris.org> (raw)
In-Reply-To: <87muq83y9t.fsf@gmail.com> (Alex Vong's message of "Sat, 17 Nov 2018 16:26:38 +0800")

Hi Alex,

Alex Vong <alexvong1995@gmail.com> writes:
> Btw, this bug report[0]
> explains why the guile bindings were removed. Although it's mark as
> wontfix, should we encourage the maintainers to re-enable the guile
> bindings in the experimental repository?

Based on:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863147#10

I think the Debian maintainers have made it clear that they will not
re-enable the Guile bindings until the underlying bug is fixed, which
apparently causes intermittent failures in GnuTLS's test suite when
Guile is built with certain compile flags, as described here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805863#84

> The problems could perhaps be solved by building the bindings with
> guile 2.2.

Sure, this would be a worthwhile thing to try, but we should probably
try it ourselves before asking the Debian developers to spend time on
it.  I can't try it easily because I use GuixSD, but if there are
interested users of Debian and Guile here, it would be a great help to
try reproducing the problem described in Debian bug 805863, and seeing
if the problem can be avoided by building GnuTLS with Debian's Guile-2.2
package.

      Regards,
        Mark


> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863147



  reply	other threads:[~2018-11-17 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  0:49 How to build GNUTLS Guile bindings on Xubuntu Zelphir Kaltstahl
2018-11-15  7:28 ` Mark H Weaver
2018-11-15 22:41   ` Zelphir Kaltstahl
2018-11-16  2:10     ` Mark H Weaver
2018-11-16  8:44     ` Alex Vong
2018-11-16 18:58       ` Mark H Weaver
2018-11-16 23:19         ` Alex Vong
2018-11-17  1:30           ` Mark H Weaver
2018-11-17  8:26             ` Alex Vong
2018-11-17 21:34               ` Mark H Weaver [this message]
2018-11-20 20:50     ` Ludovic Courtès

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=87lg5rwfpx.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=alexvong1995@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@gmail.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).