From: Ricardo Wurmus <rekado@elephly.net>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile-DRMAA 0.1.0
Date: Thu, 29 Apr 2021 08:05:53 +0200 [thread overview]
Message-ID: <87tunpmxq6.fsf@elephly.net> (raw)
In-Reply-To: <36c749d3-e156-bf68-3362-9c9b1185ead1@gmail.com>
Matt Wette <matt.wette@gmail.com> writes:
>> (You cannot *yet* get it through Guix, because there appears to
>> be a
>> regression in the excellent FFI helper included in nyacc
>> versions
>> later than 1.03.0. A guix.scm file is included in the git
>> repository that builds a slightly older version of nyacc.)
>>
> Sorry about the issues with nyacc. As part of my test I
> compile-ffi
> glib and that beast
> has been really testing my C preprocessor capability. Please
> register
> a bug report.
It’s quite likely I’m doing something silly due to the fact that
the DRMAA library isn’t available at build time. Here’s my bug
report:
https://savannah.nongnu.org/bugs/index.php?60474
Thank you!
--
Ricardo
prev parent reply other threads:[~2021-04-29 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 9:39 [ANN] Guile-DRMAA 0.1.0 Ricardo Wurmus
2021-04-29 1:34 ` Matt Wette
2021-04-29 6:05 ` Ricardo Wurmus [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://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=87tunpmxq6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-user@gnu.org \
--cc=matt.wette@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).