The install for gcc 4.8.2 flaked out a bit (libgcc_s.so.1 went missing,
during the file installation phase, and therefore bash invocations failed
with missing library errors and i later found that libstdc++.so.6 was also
missing). I have since extracted those files from gcc-4.8.2.tbz2 (because
FEATURES="buildsyspkg"), and gcc-config has run cleanly, but i now notice i
dont have cc. Is it a link/symlink? If so what's the details?

Also given this is the second time i've had a gcc installation killing
libraries, I quite like the idea of having a static bash. Since there's no
"static" use flag, i'm thinking package.env will have
app-shells/bash static.conf

and env/static.conf will be;
CFLAGS="${CFLAGS} -static"

Is there a significant downside to that approach for a machine with plenty
of RAM?

Reply via email to