Red Hat Bugzilla – Bug 160713
Missing/Incorrect BuildRequires
Last modified: 2007-11-30 17:11:07 EST
During a test rebuild of ecj-3.1-0.M4.9 in the mock builder, the following problem manifests itself: + find -name '*.class' -or -name '*.properties' -or -name '*.rsc' + xargs jar cf ../../../ecj-2.1.3.jar xargs: jar: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.45084 (%build) The reason is, that the Required libgcj installs fastjar, but doesn't set up the correct symlink with the alternatives system. This is done by the java-$ver-compat package, which is not being installed. According to nasrat the best way of dealing with this issue is dropping the BuildRequires for gcc-java and libgcj and just setting a BuildRequire for java-$ver-compat, or even better the virtual java-devel package which is provided by the java-compat package. This will fix the alternatives problem and pull in gcj and libgcj as well.
Gary, have we done this already with the java-gcj-compat virtual provide you created?
This should have been fixed in eclipse one way or another.
Andrew, can you confirm/deny/close this bug?
We currently have this in eclipse.spec: BuildRequires: java-gcj-compat-devel >= 1.0.33 Gary, is that correct?
That would do it, but you probably should have: BuildRequires: java as well, just in case you ever delete the gcj-specific stuff.
Yeah, I have that in the non-gcj_support %if block. I don't know what to do now. Shall we close this?
Make the "BuildRequires: java" unconditional and then close the bug?
I actually like things the way they are right now. If anyone feels strongly about changing it, go ahead and do it. Closing RAWHIDE.