GNU bug report logs -
#35551
package gcc does not depend on binutils and glibc
Previous Next
Reported by: Bruno Haible <bruno <at> clisp.org>
Date: Fri, 3 May 2019 22:58:01 UTC
Severity: normal
Done: Tobias Geerinckx-Rice <me <at> tobias.gr>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#35551: package gcc does not depend on binutils and glibc
which was filed against the guix package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 35551 <at> debbugs.gnu.org.
--
35551: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35551
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
Bruno,
Welcome!
Nicolas Goaziou wrote:
> You are really looking for `gcc-toolchain' package. See section
> 2.6.6 in
> the manual.
Yup! :-)
‘Toolchain’ exactly describes what you're looking for, so I'm
going to go ahead and close this bug.
(Speaking as a user, I'd be annoyed to the point of switching if
my distro installed ‘binutils’ when asked for ‘gcc’.)
Kind regards,
T G-R
[signature.asc (application/pgp-signature, inline)]
[Message part 5 (message/rfc822, inline)]
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
This bug report was last modified 6 years and 88 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.