From: Ricardo Wurmus <rekado@elephly.net>
To: ng0@n0.is
Cc: help-guix@gnu.org
Subject: Re: gnutls guile
Date: Fri, 17 May 2019 08:54:50 +0200 [thread overview]
Message-ID: <87mujlefk5.fsf@elephly.net> (raw)
In-Reply-To: <20190313175932.h363y67k5rxqsl2j@uptimegirl>
Hi ng0,
> 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.
from the original post I see that you don’t expect that triplet. From
your last two emails I don’t see why you can’t just patch it out and be
on your merry way. I also don’t see why Netbsd would change the
triplet. You wrote “This happens to make the builds and filenames more
predicatable”, but I guess you can just change this, no?
Have you attempted to stop the triplet from being changed?
--
Ricardo
next prev parent reply other threads:[~2019-05-18 10:45 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
2019-05-17 6:54 ` Ricardo Wurmus [this message]
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=87mujlefk5.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=ng0@n0.is \
/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).