Don't really know what to say else than the summary. See attached build log. Javac does really seem to be in my PATH, but "Java path" sounds very confusing to me since I never "use" java myself. I'm guessing I could solve this temporarily by disabling the java use flag for cyrus-sasl but I find this annoying so I thought I'd file a report anyway. Maybe it's me who has screwed up, but I don't think so. :) Anyway: [ebuild U ] dev-libs/cyrus-sasl-2.1.23 [2.1.22-r2] USE="berkdb crypt gdbm java mysql pam ssl -authdaemond -kerberos -ldap -ntlm_unsupported_patch -postgres -sample -srp -urandom" 0 kB [ebuild R ] dev-java/sun-jre-bin-1.6.0.14 USE="X alsa nsplugin -odbc" 0 kB !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jre-bin-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jre-bin-1.6.0.14" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" Reproducible: Always
Created attachment 193819 [details] emerge --info
Created attachment 193821 [details] build.log
I should read better. And more carefully. Especially my own build logs. "* javac is not available for sun-jre-bin-1.6 on x86_64" CRAP! However, I won't close since: emerging sun-jdk solves the problem, maybe add that as a dependency if cyrus-sasl is compiled with the java use-flag on x64?
It's strange. The ebuild specifies >=virtual/jdk-1.4 as a dependency if the java useflag is set, still I was obviously able to build (or rather, try to build ..) without such a package installed on my system (if I had virtual/jdk emerged that would've meant that I had sun-jdk installed, not sure why it didn't complain about that!). Maybe adding something like; !x86? ( >=dev-java/sun-jdk-1.6 ) Would solve the problem?
(In reply to comment #4) > Maybe adding something like; > > !x86? ( > >=dev-java/sun-jdk-1.6 ) > > Would solve the problem? > No, as virtual/jdk already depends on it (or sun-jdk-bin/icedtea6-bin). Are you able to reproduce the failure?
(In reply to comment #5) > (In reply to comment #4) > > Maybe adding something like; > > > > !x86? ( > > >=dev-java/sun-jdk-1.6 ) > > > > Would solve the problem? > > > > No, as virtual/jdk already depends on it (or sun-jdk-bin/icedtea6-bin). > > Are you able to reproduce the failure? > Yes I was multiple times before I installed sun-jdk manually. sun-jdk-bin doesn't exist in portage even. I unmerged sun-jdk just now and got the same result. Unmerging virtual/jdk made portage pull the same package and then immediately pull cyrus-sasl, which made the build fail again of course.
It seems I might have had icedtea6-bin installed at the time. Still this error was present, so I don't think this bug deserves to die in silence. The error was present with icedtea6-bin installed on the system (albeit probably not selected as the current java-vm), so this can go three ways as I see it: 1. Fix a symlink between javac and icedtea6-bin's equivalent. 2. Fix/provide detailed instructions on how to use eselect to switch the system's java-vm to icedtea6-bin before beginning the compilation. 3. Require sun-jdk to be installed if the java USE flag is enabled on cyrus-sasl. I don't think all of these are an option in practice really, afaic number 3 seems the most reasonable.
How will this be? When icedtea is installed the build obviously fails. There was a -r1 released but I haven't tested if this bug persists there, but I'd wager that is the case (no relevant changes that I can see). I'll restate what my problem was: Install dev-java/icedtea6-bin Install virtual/jdk-1.4 Install cyrus-sasl Build fails Anyone able to reproduce?
Created attachment 207387 [details] diff to fix the cyrus-sasl ebuild I got tired of waiting for this to be fixed (and I hit this EXACT SAME BUG AGAIN on my server) so here's the quick, dirty but MAKING IT WORK-solution.
This bug is caused by bug 156231. Fixed by removing virtual/jre from DEPEND.
