From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: luke hayes <luke.a.hayes@outlook.com>, help-guix@gnu.org
Subject: Re: bluez builds successfully but check fails on test-crypto.c
Date: Sat, 13 Nov 2021 11:23:13 +0100 [thread overview]
Message-ID: <a387e7e0-6e5f-d807-3b20-ee2f38e80e17@crazy-compilers.com> (raw)
In-Reply-To: <BYAPR05MB536604010686EF70FFD8B704CC8E9@BYAPR05MB5366.namprd05.prod.outlook.com>
Am 05.11.21 um 17:29 schrieb luke hayes:
> I am not sure if this is a bug or a problem related to my specific
> machine. What is the best way to fix this issue?
In these cases I typically try to understand the test-case (source) to
see whether this is an issue related to guix.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
prev parent reply other threads:[~2021-11-13 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 16:29 bluez builds successfully but check fails on test-crypto.c luke hayes
2021-11-13 10:23 ` Hartmut Goebel [this message]
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=a387e7e0-6e5f-d807-3b20-ee2f38e80e17@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
--cc=luke.a.hayes@outlook.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).