On Fri, 2008-04-25 at 18:36 +0200, Matthias Klose wrote: > As a second step please consider changing the java-gcj-compat-dev b-d > to default-jdk-builddep, making the package independent of a specific > implementation and depend on the jdk, which is most suitable for this > architecture. default-jdk-builddep will depend in addition on > java-gcj-compat-dev, even if the default jdk is another one (to allow > to compile byte-code to native code using dh_nativejava).
I just tried this, and it built fine on AMD64, but went FTBFS on at hppa where it succeeded before, because default-jdk-builddep is missing. If this is the new package to use to build across architectures, why did java-gcj-compat-dev succeed before, but this failed now? For now at least, this is creating more FTBFS than it is solving... [Also S390 has a new assertion failure in its java implementation.] Please advise, and feel free to reopen this bug if I've done something wrong. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
