all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pukkamustard <pukkamustard@posteo.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57055@debbugs.gnu.org
Subject: [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146.
Date: Mon, 08 Aug 2022 12:43:38 +0000	[thread overview]
Message-ID: <86y1vy7uvq.fsf@posteo.net> (raw)
In-Reply-To: <5ac83e05-863f-7d81-6f86-b738a7ae3fa2@telenet.be>


Maxime Devos <maximedevos@telenet.be> writes:

> [[PGP Signed Part:Undecided]]
>
> On 08-08-2022 10:36, pukkamustard wrote:
>> +    (inputs (list guile-3.0))
>
> guile-3.0 is used as a compiler, so it needs to be in native-inputs. 
> Does "guix build guile-srfi-146 --target=aarch64-linux-gnu" (or with
> another target) work?

It does not!

Adding guile-3.0 to both native-inputs and inputs seems to solve this
(also for guile-srfi-158).

However, I then get following error:

```
no code for module (srfi srfi-128)
```

guile-srfi-128 is built using the guile-build-system. Maybe something
not working properly with guile-build-system and cross-compilation?

Do you have any ideas or suggestions on how to fix this?

>> +    (license license:lgpl3+)))
>
> There are also some (ISC?) bits on
> <https://inqlab.net/git/guile-srfi-146.git/tree/srfi/srfi-146.scm>.

Yes, the sample SRFI implementation is licensed under ISC. Afaiu,
there's no problem in relicensing this as LGPL-3.0-or-later. I think a
lot of the guile-srfi-* libraries do this.

> Also, Guix does not yet install the 'LICENSES' subdirectory, see
> <https://issues.guix.gnu.org/54234#1>.

Noted.

Cheers,
pukkamustard




  reply	other threads:[~2022-08-08 13:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  8:32 [bug#57055] [PATCH 0/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08  8:36 ` [bug#57055] [PATCH 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-08  8:36   ` [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08  9:30     ` Maxime Devos
2022-08-08 12:43       ` pukkamustard [this message]
2022-08-08 13:12         ` ( via Guix-patches via
2022-08-08 13:47           ` pukkamustard
2022-08-08 18:22         ` Maxime Devos
2022-08-19 13:41           ` pukkamustard
2022-08-19 20:34             ` Maxime Devos
2022-08-29  8:48               ` pukkamustard
2022-08-08 19:04         ` Maxime Devos
2022-08-09  9:24           ` pukkamustard
2022-08-09  9:30 ` [bug#57055] [PATCH v2 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-09  9:30   ` [bug#57055] [PATCH v2 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-29  8:55 ` [bug#57055] [PATCH v3 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-29  8:56   ` [bug#57055] [PATCH v3 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-31 21:14   ` bug#57055: [PATCH 0/2] " Ludovic Courtès

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=86y1vy7uvq.fsf@posteo.net \
    --to=pukkamustard@posteo.net \
    --cc=57055@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.