From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Sam Lee <samlee746@yahoo.com>, zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Error when compiling file using Bigloo Scheme
Date: Fri, 08 Jul 2022 18:53:49 +0200 [thread overview]
Message-ID: <0d92488294f6d99006e044c988856614d323faee.camel@gmail.com> (raw)
In-Reply-To: <20220708154249.nytuihrh4m2rrvid@localhost>
Am Freitag, dem 08.07.2022 um 15:42 +0000 schrieb Sam Lee:
> On 2022-07-08 16:25 +0200, zimoun wrote:
> > On jeu., 07 juil. 2022 at 15:56, Sam Lee <samlee746@yahoo.com>
> > wrote:
> >
> > > $ bigloo myfile.scm
> > > /usr/bin/ld: cannot find -lunistring
> > > collect2: error: ld returned 1 exit status
> >
> > Indeed, bigloo requires some packages. This works for me:
> >
> > --8<---------------cut here---------------start------------->8---
> > $ guix shell -C bigloo libunistring gcc-toolchain libgc pcre \
> > -- bigloo /tmp/myfile.scm
> > --8<---------------cut here---------------end--------------->8---
>
> Thank you for providing a workaround.
>
> When I install Bigloo using Guix, shouldn't all of Bigloo's
> dependencies be installed by Guix? Why do I need to manually install
> additional packages? Is there something wrong with Bigloo's package
> definition in Guix?
We don't typically propagate packages, especially not gcc-toolchain.
You should be able to swap that out for any other toolchain, e.g.
another version of gcc-toolchain or perhaps even clang-toolchain. I'm
not sure about libunistring, libgc and pcre. There is a somewhat
similar bug in libgccjit not finding its own object files, which I find
rather silly; search paths definitely need adjusting imho.
Cheers
next prev parent reply other threads:[~2022-07-08 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220707155649.zmegt2ncimhroxxx.ref@localhost>
2022-07-07 15:56 ` Error when compiling file using Bigloo Scheme Sam Lee
2022-07-08 14:25 ` zimoun
2022-07-08 15:42 ` Sam Lee
2022-07-08 16:53 ` Liliana Marie Prikler [this message]
2022-07-11 7:29 ` zimoun
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=0d92488294f6d99006e044c988856614d323faee.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=samlee746@yahoo.com \
--cc=zimon.toutoune@gmail.com \
/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.