Why does package llvm-clang has a dependency on gcc? Can I just install llvm/clang without gcc?
–
Thanks.
yes you do need gcc you can not install without gcc it won’t work. There are reason things are dependent on other things. it is not arbitrary.
Am 31.01.2016 um 19:26 schrieb gogalthorp:
>
> yes you do need gcc you can not install without gcc it won’t work. There
> are reason things are dependent on other things. it is not arbitrary.
>
>
It is an artificial dependency introduced by compiling clang with gcc
instead of doing it with clang itself, clang is a completely from gcc
independent compiler and has also its own gcc independent linker.
@susylogin: I would consider a bug report, this is ridiculous to make
both dependent.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760 Yoga 2
Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16 HTPC: oS 42.1
x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
Am 31.01.2016 um 19:58 schrieb Martin Helm:
> It is an artificial dependency introduced by compiling clang with gcc
> instead of doing it with clang itself, clang is a completely from gcc
> independent compiler and has also its own gcc independent linker.
>
> @susylogin: I would consider a bug report, this is ridiculous to make
> both dependent.
>
I investigated a bit, my original suspicion is not correct. The
dependency comes from a few small object files which are part of the gcc
package namely the crt*.o files.
This dependency on a few kbyte pulls in the whole gcc compiler because
they are not in a separate package.
A bit of google reveals that rpm based distributions suffer from that,
while on debian based systems this files are separated into another package.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760 Yoga 2
Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16 HTPC: oS 42.1
x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
Am 31.01.2016 um 19:26 schrieb gogalthorp:
>
> yes you do need gcc you can not install without gcc it won’t work. There
> are reason things are dependent on other things. it is not arbitrary.
>
>
It is an artificial dependency introduced by compiling clang with gcc
instead of doing it with clang itself, clang is a completely from gcc
independent compiler and has also its own gcc independent linker.
@susylogin: I would consider a bug report, this is ridiculous to make
both dependent.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760 Yoga 2
Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16 HTPC: oS 42.1
x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500
Am 31.01.2016 um 19:58 schrieb Martin Helm:
> It is an artificial dependency introduced by compiling clang with gcc
> instead of doing it with clang itself, clang is a completely from gcc
> independent compiler and has also its own gcc independent linker.
>
> @susylogin: I would consider a bug report, this is ridiculous to make
> both dependent.
>
I investigated a bit, my original suspicion is not correct. The
dependency comes from a few small object files which are part of the gcc
package namely the crt*.o files.
This dependency on a few kbyte pulls in the whole gcc compiler because
they are not in a separate package.
A bit of google reveals that rpm based distributions suffer from that,
while on debian based systems this files are separated into another package.
–
PC: oS 13.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.14 | GTX 760 Yoga 2
Pro: oS 42.1 | x86_64 | i7-4500U@1.80GHz | 8GB | KDE 5.16 HTPC: oS 42.1
x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.16 | HD 2500