unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: 35551@debbugs.gnu.org
Subject: bug#35551: package gcc does not depend on binutils and glibc
Date: Sat, 04 May 2019 00:57:26 +0200	[thread overview]
Message-ID: <1666426.mZ6LCf6Yd0@omega> (raw)

Hi,

After installing the guix-1.0 installation image
(guix-system-vm-image-1.0.0.x86_64-linux) and running it with qemu,
I wanted to compile a hello-world program in C.

$ cat hello.c 
#include <stdio.h>
int main () {
  printf("Hello world\n");
  return 0;
}

$ guix install gcc
$ gcc hello.c
error trying to exec 'as': execvp: No such file or directory

Second try:
$ guix install binutils
$ gcc hello.c
/home/guest/.guix-profile/bin/ld: cannot find crt1.o: No such file or directory
/home/guest/.guix-profile/bin/ld: cannot find crt1.o: No such file or directory
collect2: error: ld returned 1 exit status

Third try:
$ guix install glibc
$ gcc hello.c
Now it succeeds!

I would have expected that 'guix install gcc' installs binutils and glibc
as well, because:
  * The use of gcc without binutils is limited: You can use "gcc -E" and "gcc -S"
    to preprocess or compile to .s files, but this is rarely what people need.
  * The use of gcc without glibc is limited: You can use "gcc -c" to compile
    to .o files. But without the ability to create a program or a shared library
    (which needs crti.o rather than crt1.o), the compiler is hardly useful.

Bruno

             reply	other threads:[~2019-05-03 22:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 22:57 Bruno Haible [this message]
2019-05-03 23:27 ` bug#35551: package gcc does not depend on binutils and glibc Nicolas Goaziou
2019-05-04  0:20   ` Tobias Geerinckx-Rice
2019-05-04  1:34     ` Bruno Haible
2019-05-07 16:23       ` Tobias Geerinckx-Rice
2019-05-07 17:26         ` Bruno Haible
2019-05-07 16:04     ` Ludovic Courtès
2019-05-09 21:21       ` Ricardo Wurmus
2019-05-09 21:57         ` Bruno Haible
2019-05-10  6:18           ` Ricardo Wurmus
2019-05-10  8:07           ` Ludovic Courtès
2019-05-10  9:38             ` bug#35551: guix search Bruno Haible
2019-05-10 10:17               ` Ludovic Courtès
2019-05-10 10:22                 ` Bruno Haible
2019-05-10 15:17                   ` Ludovic Courtès
2019-05-10 14:21                 ` Bruno Haible
2019-05-10 21:15                   ` Ludovic Courtès
2019-05-10 22:04                     ` Mark H Weaver
2019-05-10 22:38                       ` Bruno Haible
2019-05-10 23:41                         ` Tobias Geerinckx-Rice
2019-05-11 18:38                           ` Mark H Weaver
2019-05-11 18:18                         ` Mark H Weaver
2019-05-13  7:57                           ` Ludovic Courtès
2019-05-13 15:39                           ` znavko
2019-05-10 15:43                 ` znavko
2019-05-10 21:22                   ` Bruno Haible
2019-05-10 10:18               ` Bruno Haible

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=1666426.mZ6LCf6Yd0@omega \
    --to=bruno@clisp.org \
    --cc=35551@debbugs.gnu.org \
    /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).