From: raingloom <raingloom@riseup.net>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: Maxime Devos <maximedevos@telenet.be>, 46124@debbugs.gnu.org
Subject: [bug#46124] [PATCH] Idris 2
Date: Tue, 11 May 2021 23:47:34 +0200 [thread overview]
Message-ID: <20210511234734.5cf190af@riseup.net> (raw)
In-Reply-To: <87mttae83x.fsf@yoctocell.xyz>
On Tue, 04 May 2021 19:12:18 +0200
Xinglu Chen <public@yoctocell.xyz> wrote:
> On Mon, May 03 2021, raingloom wrote:
>
> > On Fri, 30 Apr 2021 10:24:42 +0200
> > Xinglu Chen <public@yoctocell.xyz> wrote:
> >
> >> On Thu, Apr 29 2021, raingloom wrote:
> >>
> >> > Here is the updated patch. No idea if this actually works cross
> >> > compiled, but I don't have much time to test it. My suspicion is
> >> > that it's likely broken and requires changes to Idris 2's code
> >> > generators, because they almost definitely call Chez, GCC, etc,
> >> > with the wrong arguments.
> >>
> >> I noticed that there is an ‘idris2_app’ directory in the ‘bin’
> >> directory
> >>
> >> $ ls /gnu/store/va62hzp46c3dp2vlcnqc7fg109axj8rq-idris2-0.3.0/bin
> >> idris2* idris2_app/
> >>
> >> What is this used for?
> >
> > If you take a look at $(guix build idris2)/bin/idris2, it's actually
> > just a wrapper. It contains the supporting dynamically linked shared
> > objects and the executable itself.
> >
> > I don't know the details of what each file does or why it's like
> > this, the codegen seems to use a similar structure for all
> > backends. The scheme files are probably all for the Chez backend,
> > the shared objects are either C libraries (for socket support and
> > stuff), or compiled Chez code. I just noticed the Racket script,
> > that I have no idea about.
> >
> > Idris 2's build system makes some... uhm... interesting choices, so
> > it's entirely possible that not all of those are necessary, or
> > could be moved somewhere more sensible.
>
> Looking at the Nix package, they remove the wrapper and instead move
> bin/idris2_app/idris2.so to bin/idris2 and wraps that executable[1].
> Perhaps we could do the same thing? I am not familiar with Idris,
> though.
>
> [1]:
> https://github.com/nixos/nixpkgs/blob//pkgs/development/compilers/idris2/default.nix#L41
That link doesn't work.
I have some more pressing projects to work on, but I'll look into it.
next prev parent reply other threads:[~2021-05-12 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 5:43 [bug#46124] [PATCH] Idris 2 raingloom
[not found] ` <87r1j267c6.fsf@yoctocell.xyz>
2021-04-26 15:22 ` raingloom
2021-04-26 21:27 ` Maxime Devos
2021-04-29 18:43 ` raingloom
2021-04-30 8:24 ` Xinglu Chen
2021-05-03 2:10 ` raingloom
2021-05-04 17:12 ` Xinglu Chen
2021-05-11 21:47 ` raingloom [this message]
2021-05-14 12:08 ` Xinglu Chen
2021-04-30 8:50 ` Maxime Devos
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=20210511234734.5cf190af@riseup.net \
--to=raingloom@riseup.net \
--cc=46124@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=public@yoctocell.xyz \
/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).