From: Manolis Ragkousis <manolis837@gmail.com>
To: rennes@openmailbox.org
Cc: help-guix@gnu.org
Subject: Re: build hello
Date: Sat, 23 Dec 2017 11:28:31 +0200 [thread overview]
Message-ID: <1f15beec-a1df-d7c7-44c5-df393aa47b6f@gmail.com> (raw)
In-Reply-To: <20171220182903.2E1794F838D@mta-1.openmailbox.org>
Hello,
On 12/20/17 20:05, rennes@openmailbox.org wrote:
> Backtrace:
> madvise failed: Function not implemented
> 16 (primitive-load "/gnu/store/lk8f1fvxblp413vyrwpl3qa73bl?")
I think this is because madvise is not implemented on Hurd and Guile is
using it. I had send a patch to workaround this on Guile [1], but I
think it never got accepted. Could you apply it on the Guile you are
using and try again?
Manolis
[1] https://lists.gnu.org/archive/html/guile-devel/2017-07/msg00001.html
next prev parent reply other threads:[~2017-12-23 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 18:05 build hello rennes
2017-12-21 15:56 ` Ludovic Courtès
2017-12-23 9:28 ` Manolis Ragkousis [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-23 15:25 rennes
2017-12-23 15:29 rennes
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=1f15beec-a1df-d7c7-44c5-df393aa47b6f@gmail.com \
--to=manolis837@gmail.com \
--cc=help-guix@gnu.org \
--cc=rennes@openmailbox.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).