GNU bug report logs - #65460
ghc/ghci are broken

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 65460 in the body.
You can then email your comments to 65460 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jonas <jonas <at> moesys.no>
To: bug-guix <at> gnu.org
Subject: ghc/ghci are broken
Date: Tue, 22 Aug 2023 22:57:37 +0000

Hi! Running ghci gives me:

GHCi, version 9.2.5: https://www.haskell.org/ghc/  :? for help
ghc: loadArchive: Not an archive: 
`/gnu/store/kqb5pmdy950b53v4ga97qvhhdfqxv9rs-glibc-2.35-static/lib/libm.a'
ghc: panic! (the 'impossible' happened)
   (GHC version 9.2.5:
     loadArchive 
"/gnu/store/kqb5pmdy950b53v4ga97qvhhdfqxv9rs-glibc-2.35-static/lib/libm.a": 
failed

Please report this as a GHC bug: https://www.haskell.org/ghc/reportabug


And compiling a hello-world program with ghc gives me:

[1 of 1] Compiling Main             ( hello.hs, hello.o )

<no location info>: error:
     Warning: Couldn't figure out C compiler information!
              Make sure you're using GNU gcc, or clang

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "(" <paren <at> disroot.org>
To: Jonas <jonas <at> moesys.no>
Cc: 65460 <at> debbugs.gnu.org, bug-guix <at> gnu.org
Subject: Re: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 06:14:50 +0100

Jonas via Bug reports for GNU Guix <bug-guix <at> gnu.org> writes:
> And compiling a hello-world program with ghc gives me:
>
> [1 of 1] Compiling Main             ( hello.hs, hello.o )
>
> <no location info>: error:
>      Warning: Couldn't figure out C compiler information!
>               Make sure you're using GNU gcc, or clang

At the risk of stating an obvious thing that you've probably already
tried; is `gcc-toolchain` available in the environment?

-- (

Message #14 received at 65460 <at> debbugs.gnu.org (full text, mbox):

From: Jonas <jonas <at> moesys.no>
To: "(" <paren <at> disroot.org>
Cc: 65460 <at> debbugs.gnu.org, bug-guix <at> gnu.org
Subject: Re: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 10:39:03 +0000

Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this 
be automatically brought in by `guix install ghc`? This does still feels 
like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?

sanoj <at> deimos ~/builds/hs-hello$ guix shell --container ghc -- ghc hello.hs
Linking hello ...

<no location info>: error:
     Warning: Couldn't figure out C compiler information!
              Make sure you're using GNU gcc, or clang
ghc: could not execute: gcc

Den 8/23/23 07:14, skrev (:
> Jonas via Bug reports for GNU Guix <bug-guix <at> gnu.org> writes:
>> And compiling a hello-world program with ghc gives me:
>>
>> [1 of 1] Compiling Main             ( hello.hs, hello.o )
>>
>> <no location info>: error:
>>       Warning: Couldn't figure out C compiler information!
>>                Make sure you're using GNU gcc, or clang
> At the risk of stating an obvious thing that you've probably already
> tried; is `gcc-toolchain` available in the environment?
>
> -- (

Message #20 received at 65460 <at> debbugs.gnu.org (full text, mbox):

From: Csepp <raingloom <at> riseup.net>
To: Jonas <jonas <at> moesys.no>
Cc: 65460 <at> debbugs.gnu.org, "\(" <paren <at> disroot.org>, bug-guix <at> gnu.org
Subject: Re: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 16:42:43 +0200

Jonas via Bug reports for GNU Guix <bug-guix <at> gnu.org> writes:

> Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this 
> be automatically brought in by `guix install ghc`? This does still feels 
> like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?
>
> sanoj <at> deimos ~/builds/hs-hello$ guix shell --container ghc -- ghc hello.hs
> Linking hello ...
>
> <no location info>: error:
>      Warning: Couldn't figure out C compiler information!
>               Make sure you're using GNU gcc, or clang
> ghc: could not execute: gcc
>
> Den 8/23/23 07:14, skrev (:
>> Jonas via Bug reports for GNU Guix <bug-guix <at> gnu.org> writes:
>>> And compiling a hello-world program with ghc gives me:
>>>
>>> [1 of 1] Compiling Main             ( hello.hs, hello.o )
>>>
>>> <no location info>: error:
>>>       Warning: Couldn't figure out C compiler information!
>>>                Make sure you're using GNU gcc, or clang
>> At the risk of stating an obvious thing that you've probably already
>> tried; is `gcc-toolchain` available in the environment?
>>
>> -- (

I assume GHC can work with other toolchains, like Clang, so it's better
to be explicit about what you want to use.

Message #26 received at 65460 <at> debbugs.gnu.org (full text, mbox):

From: Saku Laesvuori <saku <at> laesvuori.fi>
To: Csepp <raingloom <at> riseup.net>
Cc: 65460 <at> debbugs.gnu.org, paren <at> disroot.org, Jonas <jonas <at> moesys.no>
Subject: Re: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 19:16:14 +0300

[Message part 1 (text/plain, inline)]

> > Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this 
> > be automatically brought in by `guix install ghc`? This does still feels 
> > like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?

native-inputs are for buildtime inputs and here ghc needs a c toolchain
at runtime to compile another haskell program so gcc-toolchain should be
in "normal" inputs.

> I assume GHC can work with other toolchains, like Clang, so it's better
> to be explicit about what you want to use.

I think it would still be good to have a c toolchain as an input. Guix
packages are, if I understand correctly, supposed to work without having
to explicitly install their dependencies. If someone wants to use a
different c toolchain than the default, they can use a package
transformation to change it.

Maybe we could even have the current ghc as a hidden package and have
the public package wrap the hidden ghc adding gcc-toolchain to it's
environment, so that changing the c toolchain wouldn't require
rebuilding ghc.

[signature.asc (application/pgp-signature, inline)]

Message #29 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "(" <paren <at> disroot.org>
To: Jonas <jonas <at> moesys.no>
Cc: 65460 <at> debbugs.gnu.org, bug-guix <at> gnu.org
Subject: Re: bug#65460: ghc/ghci are broken
Date: Thu, 24 Aug 2023 08:01:44 +0100

Jonas <jonas <at> moesys.no> writes:
> Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this 
> be automatically brought in by `guix install ghc`? This does still feels 
> like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?

If this is to happen, it should be a regular input, and the strings
containing the programs to invoke should be replaced with their full
/gnu/store paths.

  -- (

Message #37 received at 65460-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Saku Laesvuori <saku <at> laesvuori.fi>
Cc: 65460-done <at> debbugs.gnu.org, paren <at> disroot.org, Csepp <raingloom <at> riseup.net>,
 Jonas <jonas <at> moesys.no>
Subject: Re: bug#65460: ghc/ghci are broken
Date: Tue, 29 Aug 2023 17:07:44 -0400

Hi,

Saku Laesvuori <saku <at> laesvuori.fi> writes:

>> > Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this
>> > be automatically brought in by `guix install ghc`? This does still feels
>> > like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?
>
> native-inputs are for buildtime inputs and here ghc needs a c toolchain
> at runtime to compile another haskell program so gcc-toolchain should be
> in "normal" inputs.
>
>> I assume GHC can work with other toolchains, like Clang, so it's better
>> to be explicit about what you want to use.
>
> I think it would still be good to have a c toolchain as an input. Guix
> packages are, if I understand correctly, supposed to work without having
> to explicitly install their dependencies. If someone wants to use a
> different c toolchain than the default, they can use a package
> transformation to change it.
>
> Maybe we could even have the current ghc as a hidden package and have
> the public package wrap the hidden ghc adding gcc-toolchain to it's
> environment, so that changing the c toolchain wouldn't require
> rebuilding ghc.

For building tools requiring a compiler, the current expectation across
Guix packages is that the user provides the one it wants.  Even if using
GCC, you may want to use a different version, and rebuilding GHC just to
do so is... expensive.

I'm closing, but if you'd like this to be further discussed you could
start a thread on guix-devel.

-- 
Thanks,
Maxim

Message #40 received at 65460-done <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, Saku Laesvuori
 <saku <at> laesvuori.fi>
Cc: 65460-done <at> debbugs.gnu.org, paren <at> disroot.org, Csepp <raingloom <at> riseup.net>,
 Jonas <jonas <at> moesys.no>
Subject: Re: bug#65460: ghc/ghci are broken
Date: Tue, 05 Sep 2023 19:42:34 +0200

Hi Maxim,

On Tue, 29 Aug 2023 at 17:07, Maxim Cournoyer <maxim.cournoyer <at> gmail.com> wrote:

> For building tools requiring a compiler, the current expectation across
> Guix packages is that the user provides the one it wants.  Even if using
> GCC, you may want to use a different version, and rebuilding GHC just to
> do so is... expensive.

Well, I have a patch series somewhere on my disk that adds ghc-toolchain
and hides ghc, similarly as gcc-toolchain.  Somehow, I think that, “guix
shell ghc-toolchain” should just work out-of-the-box.  And the
replacement of the C toolchain would be done with the package
transformation with-c-toolchain.

Bah, the series needs polishing…  arf!

Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.