GHC leaves GCC response files in /tmp
After building a random package with cabal, GHC leaves GCC response files in /tmp instead of deleting once done.
Here's what such a file (/tmp/cc*) looks like:
-plugin
/usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/liblto_plugin.so
-plugin-opt=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/lto-wrapper
-plugin-opt=-fresolution=/tmp/ccwHAsFF.res
-plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_s
-plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_s
--build-id
--eh-frame-hdr
--hash-style=gnu
-m
elf_x86_64
-shared
-o
dist/dist-sandbox-58bccafc/build/libHSsplit-0.2.3-1yuUfUR0BKgqOQR1FQ3Jv-ghc7.10.3.so
[...]