From: Simon Tournier <zimon.toutoune@gmail.com>
To: mikadoZero <mikadozero@yandex.com>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, 34850@debbugs.gnu.org
Subject: bug#34850: ghc compiling error
Date: Fri, 22 Sep 2023 18:09:53 +0200 [thread overview]
Message-ID: <87bkdu8a0e.fsf@gmail.com> (raw)
In-Reply-To: <tvg6s0rp.fsf@yandex.com> (mikadozero@yandex.com's message of "Wed, 13 Mar 2019 21:27:54 -0400")
Hi,
It is about this old bug #34850 [1].
1: https://issues.guix.gnu.org/issue/34850
On Wed, 13 Mar 2019 at 21:27, mikadoZero <mikadozero@yandex.com> wrote:
>>> `guix describe`
>>> guix fd4c7a0
>>> repository URL: https://git.savannah.gnu.org/git/guix.git
>>> branch: master
>>> commit: fd4c7a098a508c1de7a8513c0f3d88d5a0df12e7
[...]
>>> ```haskell
>>> main = putStrLn "hello, world"
>>> ```
>>>
>>> Then I tried to compile it with ghc. I get this error.
>>>
>>> `ghc Main` [1 of 1] Compiling Main
>>> ( Main.hs, Main.o )
>>> gcc: error trying to exec 'as': execvp: No such file or directory
>>> `gcc' failed in phase `Assembler'. (Exit code: 1)
Using recent Guix, I get:
--8<---------------cut here---------------start------------->8---
$ guix describe
Generation 28 Sep 06 2023 14:54:50 (current)
guix 6113e05
repository URL: https://git.savannah.gnu.org/git/guix.git
commit: 6113e0529d61df7425f64e30a6bf77f7cfdfe5a5
$ echo 'main = putStrLn "hello, world"' > foo.hs
$ cat foo.hs
main = putStrLn "hello, world"
$ guix shell -C ghc gcc-toolchain -- ghc foo.hs
[1 of 1] Compiling Main ( foo.hs, foo.o )
Linking foo ...
$ ./foo
hello, world
--8<---------------cut here---------------end--------------->8---
Can we close this bug report? Do you still have that issue?
Cheers,
simon
next prev parent reply other threads:[~2023-09-22 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 22:30 bug#34850: ghc compiling error mikadoZero
2019-03-13 22:48 ` Tobias Geerinckx-Rice
2019-03-14 1:27 ` mikadoZero
2023-09-22 16:09 ` Simon Tournier [this message]
2023-09-22 16:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkdu8a0e.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=34850@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=mikadozero@yandex.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.