unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: Olivier Dion <olivier.dion@polymtl.ca>,
	Greg Troxel <gdt@lexort.com>,
	Olivier Dion via General Guile related discussions
	<guile-user@gnu.org>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Subject: Re: guile-fibers timerfd_create bug (was: Re: [ANN] Guile-Parallel 1.0.0 released)
Date: Tue, 3 Jan 2023 23:43:19 +0100	[thread overview]
Message-ID: <2b8134dc-1f06-6fbe-3dd7-cb4ae7fa1b82@telenet.be> (raw)
In-Reply-To: <CADEOadfSUGbtuR=V+nk0OsPt_ipx8V5fi7L7Ht+fObe+BdVAag@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 752 bytes --]



On 03-01-2023 23:38, Damien Mattei wrote:
> no i did not test fibers  ,just look at it, but perhaps it is necessary 
> for parallel ? [...]

IIUC, it's a bug report for Guile Parallel then?

> i saw the configure file (of parallel) claim about fibers? i will download fibers and test on Mac again

To be clear, I did not propose installing Guile Fibers. AFAIK, Guile 
Fibers is not a dependency of Guile Parallel, but I didn't check.

 > If i do a :man timerfd_create on linux i got the doc in the 
manual,but > nothing on Mac os,timerfd_create seems to be part of Gnu C 
library.But > you should know that better than me.

I make no claims towards the existence or non-existence of 
timerfd_create on Mac.

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2023-01-03 22:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31  3:55 [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2022-12-31  9:06 ` Damien Mattei
2022-12-31 19:58 ` Zelphir Kaltstahl
2022-12-31 20:31   ` Olivier Dion via General Guile related discussions
2023-01-02 16:13     ` Greg Troxel
2023-01-02 17:59       ` Maxime Devos
2023-01-02 20:45         ` Greg Troxel
2023-01-02 21:24           ` Olivier Dion via General Guile related discussions
2023-01-02 23:56             ` Olivier Dion via General Guile related discussions
2023-01-03 10:57               ` Damien Mattei
2023-01-03 21:40                 ` guile-fibers timerfd_create bug (was: Re: [ANN] Guile-Parallel 1.0.0 released) Maxime Devos
2023-01-03 22:38                   ` Damien Mattei
2023-01-03 22:43                     ` Maxime Devos [this message]
2023-01-04  1:28                     ` Olivier Dion via General Guile related discussions
2023-01-03 22:06                 ` [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2023-01-03 22:29                   ` Damien Mattei
2023-01-02 20:28       ` Olivier Dion via General Guile related discussions
2023-01-08 13:30     ` Zelphir Kaltstahl
2023-01-08 14:44       ` Olivier Dion via General Guile related discussions
2023-01-08 15:17         ` Zelphir Kaltstahl
2023-01-08 15:55           ` Olivier Dion via General Guile related discussions
2023-01-08 15:59             ` Zelphir Kaltstahl

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=2b8134dc-1f06-6fbe-3dd7-cb4ae7fa1b82@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=damien.mattei@gmail.com \
    --cc=gdt@lexort.com \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=zelphirkaltstahl@posteo.de \
    /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).