Github messages for voidlinux
 help / color / mirror / Atom feed
From: VoidNoire <VoidNoire@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED]  `chez-scheme` can't be used to build `idris2` on `musl` Void
Date: Wed, 23 Dec 2020 19:13:59 +0100	[thread overview]
Message-ID: <20201223181359.25QyQMrnWFeNU_yVidrn7ujGdtRQc8-SLmuzy09O7Qg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27378@inbox.vuxu.org>

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

Closed issue by VoidNoire on void-packages repository

https://github.com/void-linux/void-packages/issues/27378

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
Void 5.9.14_1 x86_64-musl AuthenticAMD uptodate rF
  
* package:  
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
chez-scheme-9.5.4_1

### Expected behavior
Step 4 of [these steps](https://github.com/idris-lang/Idris2/blob/master/INSTALL.md) to [build `idris2` from source](https://www.idris-lang.org/idris2-src/idris2-latest.tgz) succeeds.

### Actual behavior
Step 4 fails.

### Steps to reproduce the behavior
```Shell
sudo xbps-install -S chez-scheme
curl -O https://www.idris-lang.org/idris2-src/idris2-latest.tgz
tar xf idris2-latest.tgz
cd Idris2-0.2.1
# Step 1 of the `idris2` build steps.
export PATH="$HOME/.idris2/bin:$PATH"
export LD_LIBRARY_PATH="$HOME/.idris2/lib:$LD_LIBRARY_PATH"
# Step 2 of the `idris2` build steps.
make bootstrap SCHEME=scheme
make install
# Step 4 of the `idris2` build steps. Step 3 was skipped since that only applies when step 2 isn't done.
make clean
make all && make install
```
### Other  information
We can confirm that the issue is caused by Void's `chez-scheme` package by using the `chez` package from `nix` instead, which works:

```Shell
sudo xbps-install -S nix
sudo ln -s /etc/sv/nix-daemon /var/service/
sudo sv start nix-daemon
# Add the unstable channel for `nix`.
nix-channel --add https://nixos.org/channels/nixpkgs-unstable
# Get the nix expressions from the channel.
nix-channel --update
# Install the `chez` package with `musl` compatibility.
nix-env -f channel:nixos-unstable -iA pkgsCross.musl64.chez
# Install the `idris2` package with `musl` compatibility.
nix-env -f channel:nixos-unstable -iA pkgsCross.musl64.idris2
curl -O https://www.idris-lang.org/idris2-src/idris2-latest.tgz
tar xf idris2-latest.tgz
cd Idris2-0.2.1
# Step 1 of the `idris2` build steps.
export PATH="$HOME/.idris2/bin:$PATH"
export LD_LIBRARY_PATH="$HOME/.idris2/lib:$LD_LIBRARY_PATH"
# Step 3 of the `idris2` build steps. Step 2 was skipped since we're building with an existing `idris2`.
make all
make install
# Step 4 of the `idris2` build steps.
make clean
make all && make install
```
For convenience, [here's a link to the `chez` nix expression](https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/compilers/chez/default.nix). One difference I can see between that and [Void's `chez-scheme` xbps template](https://github.com/void-linux/void-packages/blob/master/srcpkgs/chez-scheme/template) is that the latter's `configure` step doesn't use the `--threads` flag, whereas the former's does, although I'm unsure if that's the cause of the failure.

@leahneukirchen 


  parent reply	other threads:[~2020-12-23 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 16:50 [ISSUE] " VoidNoire
2020-12-23 16:59 ` leahneukirchen
2020-12-23 17:20 ` leahneukirchen
2020-12-23 17:41 ` leahneukirchen
2020-12-23 17:45 ` VoidNoire
2020-12-23 17:55 ` leahneukirchen
2020-12-23 18:13 ` VoidNoire
2020-12-23 18:13 ` VoidNoire [this message]
2020-12-23 18:19 ` leahneukirchen

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=20201223181359.25QyQMrnWFeNU_yVidrn7ujGdtRQc8-SLmuzy09O7Qg@z \
    --to=voidnoire@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).