Re: openjdk-6-6b18-1.8.5-1 binaries built
Dear Adrian,
What does this build diff's from the default openjdk-6 from packages?
http://packages.debian.org/experimental/sparc/openjdk-6-jdk/download
Thanks,
Frans van Berckel
On Thu, 2011-03-03 at 04:55 +0100, Adrian Zaugg wrote:
> Dear List
>
> After some trouble I managed to build openjdk6 for sparc64. You may
> download the debs from
>
> http://leibnitz.ethz.ch/debian/sparc64/openjdk-6/
>
> Please have a look at the README.
>
> If you want to wait for the buildd to do the job, you help me to file
> the necessary bugs, to reduce waiting time. I'm unsure against what
> packages I have to report the bugs and would appreciate your help:
>
> 1) building with fakeroot fails
> Starting the build with fakeroot debian/rules binary, throws a lot of
> errors and stops. Unfortunately I can't find the exact error anymore.
> You may build first with debian/rules build and then use fakeroot to
> produce the packages. I don't think this is bad, IIRC the buildd does it
> the same way. Should this be reported anyway?
>
> 2) sparc64 in chroot symlink missing
> As I already asked here, there is a symlink missing from /usr/lib64 to
> /usr/lib. See http://lists.debian.org/debian-sparc/2011/03/msg00003.html
> Which package is responsible for this?
>
> 3) sparc64 port naming disarrangement
> OpenJDK seems to use sparcv9 whereas Debian uses sparc64 to designate
> the 64-bit sparc plattform. I guess for this is the arch_map field in
> debian/rules, but I really don't know. I changed debian/rules to rename
> $(d)/$(basedir)/jre/lib/sparcv9 to sparc64 just before it tries to
> "install default jvm config file" - the point where building stops
> without modifying debian/rules.
> OpenJDK, when installed still searches for the original sparcv9 name,
> that's why I had to set a symlink as I described in the README from
> sparc64 to sparcv9 to turn my builds usable. Is this a bug in
> debian/rules from openjdk-6 oder does it come from somehere else?
>
> 4) dependency problems when building
> openjdk-6-jdk depends on java-access-bridge, which is not builable
> without an installed openjdk. I had to dpkg -i --force-depends
> openjdk-6-... to let libaccess-bridge-java get built. I suppose the
> maintainers know how to handle this right, or am I wrong with this opinion?
>
>
> Thank you,
> best regards, Adrian.
>
>
Reply to: