From: ng0@n0.is
To: help-guix@gnu.org
Subject: Re: gnutls guile
Date: Wed, 13 Mar 2019 17:59:32 +0000 [thread overview]
Message-ID: <20190313175932.h363y67k5rxqsl2j@uptimegirl> (raw)
In-Reply-To: <20190312002014.nwum5ryck75bi5gi@uptimegirl>
ng0@n0.is transcribed 402 bytes:
> Ludovic,
>
> as a follow-up to the short chat on #guix:
>
> if the problem can not be patched in the guile module of gnutls,
> it appears that http://git.savannah.gnu.org/cgit/guile.git/tree/module/system/base/target.scm
> could be a source of the problem?
>
> At the moment I'm trying to patch (or rather sed/awk) in gnutls
> possible occurences of the tripplet appearing with the GNU_...
> in pkgsrc.
Due to the short lifetime of IRC I'll add some more comments:
For a manual build on NetBSD (.99 being the CURRENT), the tripplet:
x86_64-unknown-netbsd8.99
is correct. For a build in pkgsrc (which is not exclusive for
NetBSD but I haven't looked at Linux behavior so far) it becomes
x86_64--netbsd8.99
because of code specified in
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/mk/configure/gnu-configure.mk?rev=1.17&content-type=text/x-cvsweb-markup
This happens to make the builds and filenames more predicatable.
So your initial assumption about NetBSD tripplets was right,
but similar to guix, pkgsrc needs a different treatment here.
Note that this is the last dependency I need to package before
can start packaging guix for pkgsrc, so it would be nice to get a patch
upstream instead of hacking around it.
The original error post:
https://lists.gnutls.org/pipermail/gnutls-help/2019-February/004488.html
I hope this is enough context to get a reply.
> Thanks,
> ng0
>
>
next prev parent reply other threads:[~2019-03-13 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 0:20 gnutls guile ng0
2019-03-13 17:59 ` ng0 [this message]
2019-05-17 6:54 ` Ricardo Wurmus
2019-05-17 8:53 ` ng0
2019-05-19 14:42 ` 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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190313175932.h363y67k5rxqsl2j@uptimegirl \
--to=ng0@n0.is \
--cc=help-guix@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).