Hi there, jakarta-jstl should emerge fine for x86 but I need it on ppc so I modify the ebuild to get it work on ppc with ibm-jdk (1.4.2_04). I described the process on a post on the forum. Also I'll add the files as attachement with this bug. If people could comment (it's my first ebuild modification) I could learn and help further (I'd like to).
Created attachment 87392 [details] jakarta jstl 1.1.2 ebuild
Created attachment 87394 [details, diff] Patch to the build.xml ant file build.xml is made for a sun-jdk. ibm break down the file rt.jar in 3 or 4 differents files.
What does the java team think about these changes?
My first impression is that the build.xml probably doesn't need to specify the bootclasspath, since it should already be setup. So, I'd suggest patching to remove the bootclasspath of javac, and see if that works on both sun-jdk and ibm-jdk.
(In reply to comment #4) > My first impression is that the build.xml probably doesn't need to specify the > bootclasspath, since it should already be setup. So, I'd suggest patching to > remove the bootclasspath of javac, and see if that works on both sun-jdk and > ibm-jdk. > Your first impression is correct. I patch to remove the classpath, and it works the same (ppc, ibm-jdk). I post the new ebuild and the patch.
Created attachment 87499 [details] new ebuild with new patch
Created attachment 87500 [details, diff] remove bootclasspath from build.xml
For future reference, it is preferred to submit patches against ebuilds, rather than the entire ebuild. This makes it possible to quickly determine how the ebuild has been changed. But I'm glad to here it could be fixed. Might I suggest you submit a bug with patch upstream as well?
Comment on attachment 87500 [details, diff] remove bootclasspath from build.xml Patch applied to ebuild in CVS.
Fixed in CVS. Thanks for reporting! Sorry about the delay.
