unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: P <pronaip@protonmail.com>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Idris packaging
Date: Wed, 21 Aug 2019 15:54:30 +0000	[thread overview]
Message-ID: <vQDKE4VkqCTJHFKmQztOvpo7u-nkl6gt27hhBhDdjbDAVokjIGJQn2OeIoHy9k9FV2Hn2iLggg_Upp_HEVUyIp9oYgJB-l29iPZGLOzctzQ=@protonmail.com> (raw)
In-Reply-To: <341839566.61098211.1566395679885.JavaMail.zimbra@centurylink.net>

On Wednesday, August 21, 2019 3:54 PM, Eric Bavier <ericbavier@centurylink.net> wrote:

> I've been able to compile Idris' generated C code by setting the, rather undocumented, IDRIS_CC environment variable, while having the 'gcc-toolchain' package installed.
>
> I have not worked much with Idris modules, so I've not encountered the deficiencies you mention. If we need to patch anything, I would prefer patching Idris to handle a list of directories in IDRIS_LIBRARY_PATH. That seems like a more flexible solution.
>
> `~Eric

Yeah, I figured that part out and got it to compile to an object file with both clang and gcc, but it doesn't always link correctly. I managed to compile a basic hello world though.
The issue is always with crti.o and crt1.o, things like GMP and pthreads and anything else passed in `-l` arguments seems to work. I can see that ld is called with these crtX.o files as regular arguments, not as -l arguments, which I guess means that it's trying to link them statically? But I don't know enough about ld to know for sure.

  reply	other threads:[~2019-08-21 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  7:24 Idris packaging P
2019-08-19  7:29 ` P
2019-08-21 13:54   ` Eric Bavier
2019-08-21 15:54     ` P [this message]
2019-08-22 13:10       ` Eric Bavier
2019-08-22 15:55         ` P

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='vQDKE4VkqCTJHFKmQztOvpo7u-nkl6gt27hhBhDdjbDAVokjIGJQn2OeIoHy9k9FV2Hn2iLggg_Upp_HEVUyIp9oYgJB-l29iPZGLOzctzQ=@protonmail.com' \
    --to=pronaip@protonmail.com \
    --cc=ericbavier@centurylink.net \
    --cc=guix-devel@gnu.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.
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).