unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: mikadoZero <mikadozero@yandex.com>
Cc: 34850@debbugs.gnu.org
Subject: bug#34850: ghc compiling error
Date: Wed, 13 Mar 2019 23:48:33 +0100	[thread overview]
Message-ID: <87tvg64chq.fsf@nckx> (raw)
In-Reply-To: <va0ms8zc.fsf@yandex.com>

mikadoZero,

mikadoZero wrote:
> `guix describe`
> guix fd4c7a0
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: fd4c7a098a508c1de7a8513c0f3d88d5a0df12e7
>
> I have ghc in my system configuration file.  I have just done a 
> pull and
> reconfigure.
>
> `which ghc`
> /run/current-system/profile/bin/ghc
>
> I created a one line hello world program:
>
> ```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)
>
> I have tested compiling the same hello world program with the 
> same ghc
> command and it works fine on a none Guix System.

Does the other system have ‘as’ installed?  Install the 
‘gcc-toolchain’ package that provides it and try again.

Usually, this kind of error means that ghc needs to be patched to 
invoke ‘as’ from an absolute file name instead of searching $PATH. 
There may have been good reasons not to do this (such as closure 
size), or it might be an oversight.

Kind regards,

T G-R

  reply	other threads:[~2019-03-13 22:57 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 [this message]
2019-03-14  1:27   ` mikadoZero
2023-09-22 16:09     ` Simon Tournier
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

  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=87tvg64chq.fsf@nckx \
    --to=me@tobias.gr \
    --cc=34850@debbugs.gnu.org \
    --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 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).