Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 831470 - net-dns/libidn-1.38-r1 fails build with `java` USE flag set
Summary: net-dns/libidn-1.38-r1 fails build with `java` USE flag set
Status: RESOLVED DUPLICATE of bug 804178
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-19 10:44 UTC by Gordon Bos
Modified: 2022-01-19 11:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
net-dns/libidn-1.3.7 build log (build.log-1.3.7,41.59 KB, application/x-troff-man)
2022-01-19 10:44 UTC, Gordon Bos
Details
net-dns/libidn-1.3.8-r1 build log (build.log-1.3.8-r1,37.07 KB, text/plain)
2022-01-19 10:44 UTC, Gordon Bos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Bos 2022-01-19 10:44:09 UTC
Created attachment 762624 [details]
net-dns/libidn-1.3.7 build log

Introduction:
I'm not really sure why, it must have made sense at some point, but I had `java` USE flag set in my global profile and when I updated libidn to 1.38-r1 the listing showed that `java` was a new USE flag for that package. Which is weird because reverting the previous version showed that this had the USE flag enabled too.

Issue:
Building the package results in an error during the configuration stage because it checks for gcj which is not functional and has not been since gcc-7.0. This check for gcj and thus on really old gcc appears to be a new build requirement for the package and I'm unsure whether this should be reported upstream as it seems impossible that the developer hasn't run into this himself if he doesn't use <gcc-7.0.
Comment 1 Gordon Bos 2022-01-19 10:44:34 UTC
Created attachment 762625 [details]
net-dns/libidn-1.3.8-r1 build log
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-01-19 11:00:48 UTC
It's found a gcj on your machine which then cannot be executed.

You probably have a stale symlink left. Newer versions of gcc-config try to warn about this.

*** This bug has been marked as a duplicate of bug 804178 ***
Comment 3 Gordon Bos 2022-01-19 11:19:42 UTC
Ah, that bug did not pop up as I searched for libidn

Strange... /usr/bin/gcj is in fact not a symlink but an ELF object. I have several other objects with the same date and size that are probably related, like:
* gc-analyze
* gcjh
* gcj-dbtool
* gjar

... and their x86_64-pc-linux-gnu- variants