From: Damien Mattei <damien.mattei@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
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:38:32 +0100 [thread overview]
Message-ID: <CADEOadfSUGbtuR=V+nk0OsPt_ipx8V5fi7L7Ht+fObe+BdVAag@mail.gmail.com> (raw)
In-Reply-To: <648df1e4-a371-ec87-7655-502c4df5aaa2@telenet.be>
no i did not test fibers ,just look at it, but perhaps it is necessary for
parallel ? i saw the configure file (of parallel) claim about fibers? i
will download fibers and test on Mac again and hope to finish reinstalling
the recent Linux tomorrow (complicated because triple boot,MacOS, Linux
kicked Windows......) I can not compare parallel and openMP because of
missing timerfd_create on mac os .
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.
On Tue, Jan 3, 2023 at 10:40 PM Maxime Devos <maximedevos@telenet.be> wrote:
>
>
> On 03-01-2023 11:57, Damien Mattei wrote:
> > on Mac os i have (only) one error:
> > In procedure dlsym: Error resolving "timerfd_create":
> > "dlsym(RTLD_DEFAULT, timerfd_create): symbol not found"
>
> Is this a bug report for Guile-Fibers? If so, could you provide basic
> information like which commit you are using, the backtrace, which file
> is being compiled (if any), ...?
>
> Also, while you can send bug reports by e-mail, if you have a GitHub
> account, then the bug tracker at https://github.com/wingo/fibers/issues
> is preferred.
>
> Greetings,
> Maxime.
>
next prev parent reply other threads:[~2023-01-03 22:38 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 [this message]
2023-01-03 22:43 ` Maxime Devos
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='CADEOadfSUGbtuR=V+nk0OsPt_ipx8V5fi7L7Ht+fObe+BdVAag@mail.gmail.com' \
--to=damien.mattei@gmail.com \
--cc=gdt@lexort.com \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
--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).