3 ms·
I certainly agree that you don't need that for production machines. However /usr/bin/gcc is just a frontend, and calls a slew of other binaries(such as cpp, co
by noselasd 10y ago
I certainly agree that you don't need that for production machines.
However /usr/bin/gcc is just a frontend, and calls a slew of other binaries(such as cpp, collect2, cc1, normally found somewhere in /usr/libexec/gcc/). You also need binutils, and to be useful, likely headers for at least the standard C library.
The gcc + binutils package comes up at around 75MB on my machine.
- makapuf 10y agoI stand corrected - duh of course I should have added called binaries. So it seems 100M is the right ballpark.