unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: jgart <jgart@dismail.de>, 65041@debbugs.gnu.org
Subject: [bug#65041] [PATCH] gnu: clisp: Add threads support on x84_64-linux.
Date: Mon, 28 Aug 2023 16:23:25 +0000	[thread overview]
Message-ID: <87zg2b9liy.fsf@kitej> (raw)
In-Reply-To: <a5ff6e10bc72ccb8b046f5c55f7fd6d550605462.1691078405.git.sharlatanus@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

Hi.

As clisp has over 1600 dependent packages, updating it should be done on
a "lisp-team" branch which will be merged into the master branch if all
goes well. However I can't do that right now as I'm on holiday until
next week.


Sharlatan Hellseher <sharlatanus@gmail.com> skribis:

> * gnu/packages/lisp.scm (clisp)[arguments]: Add configuration options to
> support threads on x86_64-linux system.
> [...]
> +                           ,@(if (string-prefix? "x86_64-linux"
> +                                                 (or (%current-system)
> +                                                     (%current-target-system)))
> +                                 '("--enable-portability"
> +                                   "--with-threads=POSIX_THREADS")
> +                                 '())

Does clisp only support threads on x86-64, or could it be enabled for
some other architectures?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2023-08-28 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 16:01 [bug#65041] [PATCH] gnu: clisp: Add threads support on x84_64-linux Sharlatan Hellseher
2023-08-26 16:14 ` [bug#65041] Sharlatan Hellseher
2023-08-28 16:23 ` Guillaume Le Vaillant [this message]
2023-08-31 13:19   ` [bug#65041] [PATCH] gnu: clisp: Add threads support on x84_64-linux Sharlatan Hellseher
2023-09-04 13:28     ` Guillaume Le Vaillant
2023-09-23  9:15       ` bug#65041: " Guillaume Le Vaillant

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=87zg2b9liy.fsf@kitej \
    --to=glv@posteo.net \
    --cc=65041@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=sharlatanus@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).