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: Fri, 16 Nov 2018 13:58:59 -0500	[thread overview]
Message-ID: <87va4wzw4x.fsf@netris.org> (raw)
In-Reply-To: <87zhu94djv.fsf@gmail.com> (Alex Vong's message of "Fri, 16 Nov 2018 16:44:20 +0800")

Hi Alex,

Alex Vong <alexvong1995@gmail.com> writes:

> Zelphir Kaltstahl <zelphirkaltstahl@gmail.com> writes:
>
>> I took another look at the page you linked to. The issue is, that I
>> would like to try Guix package manager to install GNUTLS + Guile
>> bindings, but Guix itself has the requirement of GNUTLS + Guile
>> bindings. See:
>> https://www.gnu.org/software/guix/manual/en/html_node/Requirements.html#Requirements
>>
>> So I guess I would need to somehow get GNUTLS and Guile bindings working
>> before getting Guix and then when I have Guix, I can probably somehow
>> link to the Guix installed GNUTLS and Guile bindings.
>>
>> Now I don't know where I would get the Guile bindings from. Are they
>> included in the releases on https://gnutls.org/ ?
>>
> As Mark has pointed out, if you use the binary installation of guix,
> then you can install gnutls using guix. However, I prefer to build guix
> from source. Therefore, I use the standard "configure, make, make
> install" method with appropriate CPPFLAGS, CFLAGS, CXXFLAGS and LDFLAGS
> (I include some hardending flags[0][1]):
>
>   ./configure --with-included-libtasn1 --with-included-unistring --with-guile-site-dir=/usr/local/share/guile/site/2.2
>   make
>   make check
>   make install
>
> The above works in Debian. Apart from it, you also have to build
> scheme-bytestructure, guile-git and guile-sqlite3 from source using the
> same method. Besides, it is important to keep gnutls up to date (since
> it is a piece of security-sensitive software).

Interesting.  I haven't tried building Guix from source on Debian in a
few years, but it's not clear to me how your suggestion above addresses
the original problem that Zelphir mentioned, namely that Guix requires
the Guile bindings for GnuTLS, which are not included in Debian.  I
don't see any mention of building those bindings above.  Am I missing
something?

       Mark



  reply	other threads:[~2018-11-16 18:58 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 [this message]
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
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=87va4wzw4x.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).