I compile kernel, games, programs, and libraries.
Even with all that source code present simultaneously, plus my own work on some 10+ projects and some hundred copies of that source code, I only use about 32GB. That is consistent.
With 3.5GB you could still give it a try.
If it runs out of space, it will stop compiling.
To get the space back
>> make clean
If anything got tight, just tar /usr/doc to a memory stick (probably can leave it there as most of it is boilerplate disclaimers and another copy of the same license document).
Look for internationalization files you don't use. Unless you plan on learning a foreign lanugage most of them can go.
Cut your logs down to one recent copy.
Free up /tmp memory. Many programs leave junk there.
Investigate caches in KDE and other programs. These will be wasting the most space.
All caches can be cleared or deleted.
Create a new user to do the compiling and never have that user start an X-window program.
Then tar all the other users (and their program caches in .xxx directories) out to a memory stick for the duration of the compiling.
It is not that compiling uses so much disk space, it is all the developers that waste your disk space for their program.
Last edited by selfprogrammed; 08-03-2014 at 09:30 PM.