Le jeudi 20 février 2014 à 13:45 -0500, Mike Miller a écrit :
> On Thu, Feb 20, 2014 at 11:57:51 +0100, Sébastien Villemot wrote:
> > Unfortunately octave 3.8 failed to build on kfreebsd-* and sparc so far.
> > I think it is java-related, because the default java implementation
> > changed on those arches since our last upload to experimental. I'm
> > investigating on the porterboxes.
>
> Sounds like a reasonable theory, although the error looks different
> from previous java-related failures.
I could build successfully on kfreebsd-* without Java. Still waiting for
sparc.
> The intent of depending on default-{jdk,jre} is to allow
> interoperability with OpenJDK 6 or 7 (or 8), or Oracle Java if users
> are so inclined. I haven't seen Octave work with gcj yet, I think I
> tried for myself and failed on amd64 some months ago. I guess there is
> no simpler way to express a dependency on default-{jdk,jre} as long as
> it's not gcj, but that's essentially what we will need to maintain in
> control and rules.
Indeed the culprit seems to be gcj, because kfreebsd-* and sparc
switched to gcj a few weeks ago, see:
http://packages.qa.debian.org/j/java-common/news/20140201T121827Z.html
At least until the transition is finished, I prefer that we stick to the
current scheme of expressing dependencies and maintaining them manually.
Then we could think about something better. A possibility would be to
add --disable-java at build time is the detected JDK is gcj; the
drawback is that we would have useless (build-)dependencies on
default-{jdk,jre} on the corresponding arches. Any better idea?
--
.''`. Sébastien Villemot
: :' : Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part