unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] Guile-Parallel 1.0.0 released
Date: Sun,  8 Jan 2023 13:30:59 +0000	[thread overview]
Message-ID: <f7a452c5-07c5-9eca-6238-4caaa50908e5@posteo.de> (raw)
In-Reply-To: <87pmbzpb6h.fsf@laura>

On 12/31/22 21:31, Olivier Dion wrote:
> On Sat, 31 Dec 2022, Zelphir Kaltstahl<zelphirkaltstahl@posteo.de>  wrote:
>
>> Maybe I can already make use of it in coming AoC puzzles.
> Any sort of feeback is welcome!

Hello Olivier!

May I ask how to make use of the library? I cloned the project onto my local 
machine in a subfolder of a project, in which I want to use it. There are some 
guix files in the guile-parallel repository, but I am unsure how to make use of 
it as a guix package. I think there was a possibility to use local code as a 
package in a guix shell, but I cannot find the info how to do it, so I tried the 
following:

~~~~
# from the main dir of my project
# guile-parallel is cloned into the subfolder guile-parallel
# so basically: git clone git-repo-url, nothing more

guix shell -L guile-parallel guile -- guile -L .
%%%% Starting test (parallel atomic)  (Writing full log to "(parallel atomic).log")

~~~~

At that step it hangs. Doesn't do anything. Does not put load on my CPU, just hangs.

Maybe I am doing it wrong.

Best regards,
Zelphir

-- 
repositories:https://notabug.org/ZelphirKaltstahl


  parent reply	other threads:[~2023-01-08 13:30 UTC|newest]

Thread overview: 23+ 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
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2023-01-03 16:47 dsmich

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=f7a452c5-07c5-9eca-6238-4caaa50908e5@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).