system/gcc: problems getting GCC to work
Bugzilla ID | 27 |
Reporter | Samuel Holland |
Assignee | A. Wilcox (awilfox) |
Reported | 2017-02-01 13:59:11 -0600 |
Modified | 2017-11-24 22:44:59 -0600 |
Status | RESOLVED FIXED |
Version | 1.0-ALPHA1 |
Hardware | Adélie Linux / All |
Importance | Normal / normal |
Description
I installed gcc5.4.0, hoping to get a working compiler. Here are the issues I faced:
- No GCC profile is set by default, meaning there was no cc or gcc symlink. This can be set with gcc-config.
- gcc-config refused to run because it could not determine the CHOST. I got around this by exporting CHOST on the command line based on the output of
gcc-5.4.0 -v
- After that, I noticed that gcc failed when it tried to run
as
because binutils also has no default version set. - binutils-config cannot list possible profiles because CHOST is not set (and portageq is not found when it tries to auto-detect CHOST).
- Once that is fixed, gcc cannot find libgcc. This is because libgcc.a is in the gcc5.4.0-devel package, which gcc5.4.0 does not depend on.
- Also, musl-devel is not pulled in by any of these packages; I'm not sure if that is intended.