From: Simon Tournier <zimon.toutoune@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 55178@debbugs.gnu.org, christoph.schumacher@mathematik.tu-dortmund.de
Subject: bug#55178: ghc cannot find libraries of ghc-comonad
Date: Fri, 22 Sep 2023 18:45:04 +0200 [thread overview]
Message-ID: <87wmwi6ttb.fsf@gmail.com> (raw)
In-Reply-To: <Y8vfWWxaFlPPJu6s@noor.fritz.box> (Lars-Dominik Braun's message of "Sat, 21 Jan 2023 13:49:29 +0100")
Hi Christoph,
On Sat, 21 Jan 2023 at 13:49, Lars-Dominik Braun <lars@6xq.net> wrote:
>> guix shell --pure ghc ghc-comonad gcc-toolchain -- ghc LinkMe.hs
>> [1 of 1] Compiling Main ( LinkMe.hs, LinkMe.o )
>> Linking LinkMe ...
>> ld: cannot find -lHScomonad-5.0.8-KDPzf2kORSz9Qeif8nQH6d
>> ld: cannot find -lHStransformers-compat-0.6.6-9ADqfwGTALm8Nq2ZeUpa4p
>> ld: cannot find -lHSindexed-traversable-0.1.1-Dfr00dUbJtB3rFEVdhtcE9
>> ld: cannot find -lHSdistributive-0.6.2.1-L7rr3EplzD03NITUnJxmCO
>> ld: cannot find -lHStagged-0.8.6.1-EiQY3za6Q5HE9cdvqupke2
>> ld: cannot find -lHSbase-orphans-0.8.5-Iz1X6ZIULaHC76vf03czEu
>> collect2: error: ld returned 1 exit status
>> `gcc' failed in phase `Linker'. (Exit code: 1)
>
> the problem here is that in Guix we link Haskell executables dynamically
> and sometimes move static libraries to a separate output without updating
> the config file (because otherwise it would create a reference, which
> we’re trying to avoid to save space).
>
> It works fine for me using
>
> guix shell --pure ghc ghc-comonad gcc-toolchain@10 -- ghc --make -dynamic -v LinkMe.hs
Does it fix your issue report in #55178?
https://issues.guix.gnu.org/issue/55178
Closing?
Cheers,
simon
next prev parent reply other threads:[~2023-09-22 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 1:39 bug#55178: ghc cannot find libraries of ghc-comonad Christoph Schumacher
2023-01-21 12:49 ` Lars-Dominik Braun
2023-09-22 16:45 ` Simon Tournier [this message]
2023-10-03 21:29 ` cschumac
2023-10-04 17:59 ` Simon Tournier
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=87wmwi6ttb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=55178@debbugs.gnu.org \
--cc=christoph.schumacher@mathematik.tu-dortmund.de \
--cc=lars@6xq.net \
/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).