also possibly a problem with sys-devel/gcc-6.*.0; the url listed explains the problem pretty well, but in brief there are some definitions which differ enough between the two to keep it from compiling.
cfns.gperf: In function ‘const char* libc_name_p(const char*, unsigned int)’:
cfns.gperf:101:1: error: ‘const char* libc_name_p(const char*, unsigned int)’ redeclared inline with ‘gnu_inline’ attribute
cfns.gperf:26:14: note: ‘const char* libc_name_p(const char*, unsigned int)’ previously declared here
Steps to Reproduce:
2. follow prompts
3. get to sys-devel/gcc-5.3.0::gentoo_prefix
gcc compilation halts due to the above declaration issues.
gcc compilation to continue until completion, and then carrying on with the process of bootstrapping a prefix.
This is a fairly trivial fix; I will be attaching a patch that will fix it for gcc-5.3.0 as presented by ::gentoo_prefix, or barring that you can update gcc in the prefix overlay to at least sys-devel/gcc-5.4.0, which does not appear to require this patch based on my inspection.
Created attachment 496336 [details, diff]
a rebased version of https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=233572
Created attachment 496338 [details]
build.log for gcc-6.4.0
Confirmed to affect building with gcc-6.4.0 as well.
Created attachment 496340 [details]
build.log for gcc-7.1.0
Well, this is the very reason I have gcc-4.9 still selected here...
The bug has been closed via the following commit(s):
Author: Michael Haubenwallner <firstname.lastname@example.org>
AuthorDate: 2017-09-25 16:39:25 +0000
Commit: Michael Haubenwallner <email@example.com>
CommitDate: 2017-09-25 16:39:25 +0000
sys-devel/gcc: build 5.3.0 with 7.1.0 host
Package-Manager: Portage-2.3.10-prefix, Repoman-2.3.3
sys-devel/gcc/files/gcc-5.3.0-libc_name_p.patch | 111 ++++++++++++++++++++++++
sys-devel/gcc/gcc-5.3.0.ebuild | 1 +
2 files changed, 112 insertions(+)
(In reply to hanetzer from comment #1)
Thanks a lot for the patch!