Am 05.12.2017 um 19:13 schrieb Andreas Tille:
> On Tue, Dec 05, 2017 at 07:05:23PM +0100, Emmanuel Bourg wrote:
>> Le 05/12/2017 à 18:48, Andreas Tille a écrit :
>>
>>> So either I'm doing this CLASSPATH definition wrong or it does not help.
>>
>> I think you have to use "export CLASSPATH" in debia
On Tue, Dec 05, 2017 at 07:05:23PM +0100, Emmanuel Bourg wrote:
> Le 05/12/2017 à 18:48, Andreas Tille a écrit :
>
> > So either I'm doing this CLASSPATH definition wrong or it does not help.
>
> I think you have to use "export CLASSPATH" in debian/rules
No change. :-(
--
http://fam-tille.de
Le 05/12/2017 à 18:48, Andreas Tille a écrit :
> So either I'm doing this CLASSPATH definition wrong or it does not help.
I think you have to use "export CLASSPATH" in debian/rules
On Tue, Dec 05, 2017 at 02:13:59PM +0100, Emmanuel Bourg wrote:
> Le 05/12/2017 à 14:09, Andreas Tille a écrit :
>
> > Should I approach upstream about this issue? I'm not sure whether I'll
> > just get the hint to use JAR files shipped with the source tarball ...
> > :-(
>
> First check if bati
Le 05/12/2017 à 14:09, Andreas Tille a écrit :
> Hmmm, the lib/batik*.jar files removed from the upstream tarball contain
> files from 2008 - one of these has version 1.7 in the file name while I
> was building against 1.9.
>
> Should I approach upstream about this issue? I'm not sure whether I'
Hi Emmanuel,
On Tue, Dec 05, 2017 at 11:47:37AM +0100, Emmanuel Bourg wrote:
> > Any hint how to solve this one?
>
> I don't know, maybe it needs a more recent version of Batik?
Hmmm, the lib/batik*.jar files removed from the upstream tarball contain
files from 2008 - one of these has version 1.
Le 05/12/2017 à 11:31, Andreas Tille a écrit :
> A, thanks a lot for reading aloud the docs for me (and sorry for
> bothering you about this :-( ).
No need to be sorry, this wasn't obvious ;)
> Any hint how to solve this one?
I don't know, maybe it needs a more recent version of Batik?
Hi Emmanuel,
On Tue, Dec 05, 2017 at 11:06:23AM +0100, Emmanuel Bourg wrote:
> Hi Andreas,
>
> You have to build depend on openjfx, not libopenjfx-java. The
> description of libopenjfx-java has this:
>
> "This package contains the Java libraries only, installing it won't add
> the JavaFX classes
Le 05/12/2017 à 10:58, Andreas Tille a écrit :
> I have added libopenjfx-java to Build-Depends but most probably
> something needs to be added to build.xml. Unfortunately I have
> not understood how to use libopenjfx-java properly. Any hint how
> to get igv building properly?
Hi Andreas,
You h
control: tags -1 pending
On Sat, Oct 07, 2017 at 06:25:29PM +0200, Andreas Beckmann wrote:
> Source: igv
> Version: 2.3.90+dfsg-1
> Severity: serious
> Tags: sid buster
> Justification: fails to build from source
>
> Hi,
>
> igv recently started to FTBFS in sid:
>
> compile:
> [javac] Compi
Processing control commands:
> tags -1 pending
Bug #877941 [src:igv] igv: FTBFS: SVGTest.java:111: error: cannot access
Localizable
Added tag(s) pending.
--
877941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: igv
Version: 2.3.90+dfsg-1
Severity: serious
Tags: sid buster
Justification: fails to build from source
Hi,
igv recently started to FTBFS in sid:
compile:
[javac] Compiling 893 source files to /build/igv-2.3.90+dfsg/tmp
[javac] warning: [options] bootstrap class path not set in c
12 matches
Mail list logo
