public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Andrey Grozin <grozin@woodpecker.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 12:11:51 +0200	[thread overview]
Message-ID: <uwmyrvswo@gentoo.org> (raw)
In-Reply-To: <d519264a-7891-c32f-5097-7ebfd8bc47f@woodpecker.gentoo.org> (Andrey Grozin's message of "Sun, 23 Jul 2023 09:41:21 +0000 (UTC)")

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

>>>>> On Sun, 23 Jul 2023, Andrey Grozin wrote:

> OK, sbcl is masked on musl. But why clisp, ecls, or gcl cannot be used
> in the amd64 musl profile?

> (I don't know if they actually work on amd64 musl systems, or if
> anybody ever tried to do so. I just ask a formal question about Gentoo
> profiles system.)

pkgcheck's mesage was this:

  RequiredUseDefaults: version 5.47.0: profile: 'default/linux/amd64/17.0/musl' (3 total) failed REQUIRED_USE: ( clisp || clozurecl || clozurecl64 || cmucl || ecls || gcl || sbcl )

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.

Moving the + from sbcl to e.g. clisp would get rid of the message, but
maybe this is not an acceptable solution.

Ulrich

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

  reply	other threads:[~2023-07-23 10:12 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 [this message]
2023-07-23 10:14       ` Ulrich Mueller
2023-07-23 10:28       ` Andrey Grozin
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=uwmyrvswo@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=grozin@woodpecker.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