O GCC/G++ do Fedora faz um tipo de cache, existe algo similar no Debian? [RESOLVIDO]

zhushazang escreveu:

Rapaz, você está usando gcc-5. Confere a versão no Debian e compare com o mesmo comando (gcc -v). Acho que a comparação é indevida. Houve otimização no gcc, mas a versão 5, por aqui é "very unstable" e no Debian provavelmente a mesma coisa.

Atenciosamente

---
Hail Hydra!

RUN MODES
There are two ways to use ccache. You can either prefix your compilation commands with ccache or you can let
ccache masquerade as the compiler by creating a symbolic link (named as the compiler) to ccache. The first
method is most convenient if you just want to try out ccache or wish to use it for some specific projects. The
second method is most useful for when you wish to use ccache for all your compilations.

To use the first method, just make sure that ccache is in your PATH.

To use the symlinks method, do something like this:

cp ccache /usr/local/bin/
ln -s ccache /usr/local/bin/gcc
ln -s ccache /usr/local/bin/g++
ln -s ccache /usr/local/bin/cc
ln -s ccache /usr/local/bin/c++

And so forth. This will work as long as the directory with symlinks comes before the path to the compiler
(which is usually in /usr/bin). After installing you may wish to run “which gcc” to make sure that the correct
link is being used.

Warning
The technique of letting ccache masquerade as the compiler works well, but currently doesn’t interact well
with other tools that do the same thing. See USING CCACHE WITH OTHER COMPILER WRAPPERS.

Warning
Do not use a hard link, use a symbolic link. A hard link will cause “interesting” problems.

$ file /usr/bin/g++

/usr/bin/g++: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=9ef56fc78e6d74ee928d6b4a1e1f34387a7bc6f0, stripped 

-C, --clear
Clear the entire cache, removing all cached files, but keeping the configuration file.