We'd like to kill SYMLINK_LIB support completely. Please look into preparing a new 17.1 profiles that don't use that.
You may check if app-portage/unsymlink-lib tool can be of use. It's been made for amd64 but it might work for ppc64 as well if the layout is compatible enough. If you need some changes to make it work on ppc64, let me know.
At the very least we will need to recover from 17.0 breakage: bug #641474
Well, there's no reason why you couldn't disable SYMLINK_LIB while staying with the 'old' gcc.
Looks good to go according to my testing. I'll make some 17.1 profiles for ppc64.
new profiles are here ready for review
I did not go with 17.1 name as I'm flattening and changing structure anyway, not sure it's really needed.
taking bug, I'm working on it.
moving ppc64 to CC. sorry for spam.
The bug has been referenced in the following commit(s):
Author: Georgy Yakovlev <email@example.com>
AuthorDate: 2020-09-20 02:59:51 +0000
Commit: Georgy Yakovlev <firstname.lastname@example.org>
CommitDate: 2020-09-20 03:00:45 +0000
app-portage/unsymlink-lib: add ~ppc64 keyword
Package-Manager: Portage-3.0.7, Repoman-3.0.1
Signed-off-by: Georgy Yakovlev <email@example.com>
app-portage/unsymlink-lib/unsymlink-lib-18.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)