public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrey Grozin <grozin@woodpecker.gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] are there any lisps in the default/linux/amd64/17.0/musl profile?
Date: Sun, 23 Jul 2023 10:28:30 +0000 (UTC)	[thread overview]
Message-ID: <6e5429b2-36bd-cb65-e46d-960be6d564@woodpecker.gentoo.org> (raw)
In-Reply-To: <uwmyrvswo@gentoo.org>

On Sun, 23 Jul 2023, Ulrich Mueller wrote:
> I think what happens is this: sbcl is masked on musl, but it is the only
> version that is enabled in the ebuild by the IUSE="+sbcl" default.
> Therefore, none of the versions available on musl is enabled there,
> resulting in an unsatisfied REQUIRED_USE.
Thank you. Probably, pkgcheck complains because of +sbcl, and sbcl is 
masked. sbcl is the best lisp for maxima on systems where it exists, 
therefore it is the default. If it does not exist, a user can try some 
other lisp. So, I'm going to continue to ignore this complaint.

By the way, I've just found (and fixed) another minor problem. Due to some 
(uninteresting) technical reasons, clozurecl in maxima ebuild is 
controlled by the use flags clozurecl (on 32-bit arches) and clozurecl64 
(on 64-bit arches). The clozurecl flag is masked in arch/base/use.mask and 
unmasked in arch/x86/use.mask (correctly). But clozurecl was not 
controlled in the same way. Now I mask it in arch/base/use.mask and unmask 
in arch/amd64/use.mask.

Andrey


  parent reply	other threads:[~2023-07-23 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23  9:20 [gentoo-dev] are there any lisps in the default/linux/amd64/17.0/musl profile? Andrey Grozin
2023-07-23  9:26 ` Ulrich Mueller
2023-07-23  9:41   ` Andrey Grozin
2023-07-23 10:11     ` Ulrich Mueller
2023-07-23 10:14       ` Ulrich Mueller
2023-07-23 10:28       ` Andrey Grozin [this message]
2023-07-24  0:13       ` Violet Purcell

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6e5429b2-36bd-cb65-e46d-960be6d564@woodpecker.gentoo.org \
    --to=grozin@woodpecker.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@gentoo.org \
    /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