| Summary: | sys-devel/gcc-6.3.0 untracked / duplicated gcc binaries | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nick Kossifidis <mickflemm> |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | fturco, jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Well, some of them should be symlinks generated by gcc-config ... Is /usr/bin/x86_64-pc-linux-gnu-gcc a symlink? where does it point? do you have gcc-6.3 selected with gcc-config? Please check this, if you still think something's wrong please reopen the bug. |
I'm using Gentoo hardened and recently, after I updated my system (emerge-webrsync + emerge -vauDN world) I scanned my system for orphaned files. I noticed that gcc binaries on /usr/bin are not tracked by portage (qfile -o reports them) and also exist two times, one with the chost prefix and one without. Also both versions are different (have different md5sums) that the (tracked) binaries in /usr/${CHOST}. What's going on ? Is this the expected behavior ? Reproducible: Always Actual Results: md5sum /usr/bin/x86_64-pc-linux-gnu-gcc cd172542f09ffc3cb88a7bb75f82cf00 /usr/bin/x86_64-pc-linux-gnu-gcc md5sum /usr/bin/gcc cd172542f09ffc3cb88a7bb75f82cf00 /usr/bin/gcc md5sum /usr/x86_64-pc-linux-gnu/gcc-bin/6.3.0/x86_64-pc-linux-gnu-gcc f9cbcf3950a42cd8b7fc8e277ec29990 /usr/x86_64-pc-linux-gnu/gcc-bin/6.3.0/x86_64-pc-linux-gnu-gcc