bug#32131: ghc fails to compile packages when installed into profile

bug#32131: ghc fails to compile packages when installed into profile

[Anonymous]

This bug can be reproduced by doing

     guix package -i ghc
     echo 'main=return()' > test.hs
     ghc test.hs

The expected output is that the program will be compiled, but instead we 
get the error message

     gcc: error trying to exec 'as': execvp: No such file or directory
     `gcc' failed in phase `C Compiler'. (Exit code: 1)

The error is caused, of course, by as not being found in the path. 
Interestingly, though, the error occurs in gcc, which fails to find as. 
The general path for compiling things with gcc is to use gcc-toolchain, 
which brings as and others into the profile, but as ghc calls gcc 
directly (with no gcc-toolchain), ghc fails to actually compile anything.

bug#32131: ghc fails to compile packages when installed into profile

[Ludovic Courtès]

Hello,

Anonymous <mcrfan96@cock.li> skribis:

> This bug can be reproduced by doing
>
>     guix package -i ghc
>     echo 'main=return()' > test.hs
>     ghc test.hs
>
> The expected output is that the program will be compiled, but instead
> we get the error message
>
>     gcc: error trying to exec 'as': execvp: No such file or directory
>     `gcc' failed in phase `C Compiler'. (Exit code: 1)
>
> The error is caused, of course, by as not being found in the
> path. Interestingly, though, the error occurs in gcc, which fails to
> find as. The general path for compiling things with gcc is to use
> gcc-toolchain, which brings as and others into the profile, but as ghc
> calls gcc directly (with no gcc-toolchain), ghc fails to actually
> compile anything.

Indeed.  Does running:

  guix package -i glibc binutils ld-wrapper

help?

Regardless I agree that it should just work.

Thanks for reporting the issue,
Ludo’.

bug#32131: ghc fails to compile packages when installed into profile

[Hogenson, Raymond E (334H-Affiliate)]

On 7/12/18, 8:59 AM, "Ludovic Court=C3=A8s" <ludo@gnu.org> wrote:
> Hello,
>
> Anonymous <mcrfan96@cock.li> skribis:
>
> [...]
>
> Indeed.  Does running:
>
>   guix package -i glibc binutils ld-wrapper
>
> help?

Actually, it does not. Doing that, I get the error

    ld: cannot find crt1.o: No such file or directory
    ld: cannot find crti.o: No such file or directory
    collect2: error: ld returned 1 exit status
    `gcc' failed in phase `Linker'. (Exit code: 1)

However, if I also set

    LIBRARY_PATH=<path to glibc>/lib

then compilation proceeds just fine. It seems like just bringing glibc
into the profile does not correctly set LIBRARY_PATH.

bug#32131: ghc fails to compile packages when installed into profile

[Simon Tournier]

Hi,

This old bug #32131,

    https://issues.guix.gnu.org/issue/32131

is not a bug.  It is because gcc-toolchain is missing.

On Wed, 11 Jul 2018 at 22:12, Anonymous <mcrfan96@cock.li> wrote:
> This bug can be reproduced by doing
>
>     guix package -i ghc
>     echo 'main=return()' > test.hs
>     ghc test.hs
>
> The expected output is that the program will be compiled, but instead we get
> the error message

--8<---------------cut here---------------start------------->8---
$ echo 'main=return()' > test.hs

$ guix shell -C ghc gcc-toolchain -- ghc test.hs
[1 of 1] Compiling Main             ( test.hs, test.o )
Linking test ...

$ ./test
--8<---------------cut here---------------end--------------->8---

Closing.  Let me know if I am missing something.

Cheers,
simon