Summary: | sys-devel/gcc-config: obsolete /usr/bin/gcj (was: net-dns/libidn-1.38-r1[java]: configure: error: The Java compiler gcj -C failed) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Craig Andrews <candrews> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugzilla, candrews, mgorny, sam |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/22985 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build
build.log config.log |
Description
Craig Andrews
2021-07-25 14:24:26 UTC
Created attachment 726916 [details]
build
Created attachment 726919 [details]
build.log
Created attachment 726922 [details]
config.log
On my system this seemed to be due to an orphaned /usr/bin/gcj executable. I did ‘rm /usr/bin/gcj’ to deal with that. (In reply to Barry Schwartz from comment #4) > On my system this seemed to be due to an orphaned /usr/bin/gcj executable. > > I did ‘rm /usr/bin/gcj’ to deal with that. I would imagine the problem was really with gcc-config not deleting the file at some distant past time. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6f46c580900c559ff34f27f4118e9bb70b510c8b commit 6f46c580900c559ff34f27f4118e9bb70b510c8b Author: Sam James <sam@gentoo.org> AuthorDate: 2021-11-18 09:25:39 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-11-22 07:07:23 +0000 sys-devel/gcc-config: warn on obsolete gcj wrapper Bug: https://bugs.gentoo.org/804178 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/22985 Signed-off-by: Sam James <sam@gentoo.org> ...gcc-config-2.5.ebuild => gcc-config-2.5-r1.ebuild} | 8 ++++++++ sys-devel/gcc-config/gcc-config-9999.ebuild | 19 +++++++++---------- 2 files changed, 17 insertions(+), 10 deletions(-) *** Bug 831470 has been marked as a duplicate of this bug. *** |