Source: openjdk-6 Version: 6b24~pre2-1 Severity: wishlist User: [email protected] Usertags: alpha X-Debbugs-CC: [email protected]
Openjdk-6 for the Alpha port build depends on itself, presumably to bootstrap it. That is currently a problem for the build daemons as openjdk-6 is not installable due to missing dependencies, thus is bd-uninstallable---a tight unbreakable dependency loop. I probably could get it built by creating a special purposed chroot with the missing dependencies from snapshot.d.o, but I noticed that on the majority of arches openjdk-6 build depends on gcj for bootstrapping thus it can be built without an older version of itself. So I am left wondering, why does openjdk-6 build depend on itself on Alpha? Is there some historical (hysterical?) reason for that? Why not use gcj to bootstrap it on Alpha? As an experiment I modified the source of version 6b24~pre2-1 to bootstrap with gcj on Alpha. It sucessefully complete debian/rules build, but failed in debian/rules binary with: dh_install --sourcedir=debian/tmp --fail-missing -XLICENSE dh_install: cp -a debian/tmp/usr/lib/jvm/java-6-openjdk-alpha/jre/lib/rt.jar debian/openjdk-6-jre-headless//usr/lib/jvm/java-6-openjdk-alpha/jre/lib/ died with signal 11 make: *** [install] Error 2 Is that a major flaw (hence why it bootstraps with openjdk-6 on Alpha) or just an indication that I cocked up the modifications to debian/rules and debian/control in my experiment? Cheers Michael. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
