Bug 73319 - dev-java/bcel-5.1 fails
|
Bug#:
73319
|
Product: Gentoo Linux
|
Version: 2004.1
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: normal
|
Priority: P1
|
|
Resolution: FIXED
|
Assigned To: java@gentoo.org
|
Reported By: hetfield666@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-java/bcel-5.1 fails
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-12-04 02:56 0000
|
after log4j unlock i tried to emerge eclipse
but bcel failed.
always with jdk 5.0!
I do not understand the problem. Please state your problem clearly and
completely
so that may attempt to reproduce it.
In particular, list the versions of the packages involved, and all pertaining
error messages.
sorry, i haven't my notebook so i can't try again:
infos:
jdk 5.0
trying to compile it gives errors, the "usual ones"
like enum and so on...
and compilation fails.
i searched for a newer version, but seems 5.1 is the lastest.
patch needed so.
Presumably, the build.xml needs to be patched with source/target=1.4 (or
older).
found a solution.
a) USE="-jikes" or will create so many errors.
b) search the sources for "Deprecated" class. it's in 2 files only.
Pass2verifier and String[...]
i don't remember exactly...i did the patch on a friend's pc.
changed the Deprecated class into "org.apache.bcel.classfile.Deprecated"
and it will compile good.
should be 5 occorrences only.
i did manually and so i can't provide a patch.
(of course this is for jdk 5.0, but will work with older versons too. it's due to java.lang.Deprecated class, so Deprecated will be ambigous).
please apply asap.
Created an attachment (id=46350) [details]
bcel-5.1.ebuild
a new ebuild which doesnt make use of the CLASSPATH=foo... thing. i've also
done some other cleanups and the most important it applies two patches.
Created an attachment (id=46351) [details]
bcel-5.1-gentoo-buildxml.diff
this patch adds source and target attributes to the javac nodes and adds a
reference to ${regexp.jar} to the build.xml. by doing it this way we can simply
add regexp.jar=... to the build.properties file inside of the ebuild.