Re: subversion 1.2.3a for sarge?

From: Anders Lennartsson (anders.lennartsson_at_foi.se)
Date: 09/30/05

  • Next message: Adam Funk: "Re: aptitute "Unable to correct dependencies" -- how to fix?"
    Date: Fri, 30 Sep 2005 11:18:10 +0200
    To: "Roberto C. Sanchez" <roberto@familiasanchez.net>, debian-user@lists.debian.org
    
    

    Thanks for the effort.

    I did discover the same problem. My solution was to use Sun's Java
    packaged with java-package instead of kaffe. Then the compile went
    fine, including all checks. (Though I wasn't planning to use javahl
    so I could just have avoided building this package.)

    I simply changed the line

    confflags += --enable-javahl --without-jikes --with-jdk=/usr/lib/kaffe

    to

    confflags += --enable-javahl --without-jikes --with-jdk=/usr/lib/j2sdk1.4-sun

    in debian/rules.

    With sid, the original 1.2.3a builds fine so I guess the kaffe(?) bug
    has been fixed there.

    Others have mentioned good experiences from using (rebuilt) 1.2.3a on
    sarge systems, so I think it is just fine to go ahead.

    Anders

    On Mon, 2005-09-26, at 18:45:42 -0400, Roberto C. Sanchez wrote:
    > On Wed, Sep 21, 2005 at 04:55:28PM +0200, Anders Lennartsson wrote:
    > > Does it break anything essential to build and use the sources for
    > > subversion 1.2.3a, found in sid, for sarge? The build dependencies in
    > > debian/control can be met on a properly maintained sarge box, but
    > > perhaps this may not be the full truth or?
    > >
    >
    > I just tried to build it in a Sarge chroot and here is the result:
    >
    > /tmp/buildd/subversion-1.2.3a/build-tree/subversion-1.2.3/subversion/bindings/java/javahl/native/JNIByteArray.cpp:80: error: invalid
    > conversion from `jbyte*' to `const signed char*'
    > make[1]: *** [subversion/bindings/java/javahl/native/JNIByteArray.lo] Error 1
    > make[1]: Leaving directory `/tmp/buildd/subversion-1.2.3a/build-tree/subversion-1.2.3'
    > make: *** [debian/stamp-build] Error 2
    > pbuilder: Failed autobuilding of package
    >
    > I imagine that if you took the time to track down the error and patch
    > the package, then you could make it work.
    >
    > -Roberto
    > --
    > Roberto C. Sanchez
    > http://familiasanchez.net/~roberto

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Adam Funk: "Re: aptitute "Unable to correct dependencies" -- how to fix?"

    Relevant Pages

    • On Free Java Implementations (was: Re: Blackdown)
      ... Yes, not only that, but Kaffe is also in testing, which means that it has ... the state of Free implementations of Java is getting better all ... the time and I even got some free time to package ppower4 and put it on ...
      (Debian-User)
    • Re: subversion 1.2.3a for sarge?
      ... > packaged with java-package instead of kaffe. ... > so I could just have avoided building this package.) ... I built it inside of a Sarge pbuilder chroot, which uses kaffe ...
      (Debian-User)
    • Re: Dynamic Plug-in Loading with Ada
      ... Ada under GNAT/Linux. ... The package implemented procedures to run statements, ... compile subprograms and to compile packages. ... unsuited to Live Coding, but it *can* be made to work. ...
      (comp.lang.ada)
    • Re: Modelsim : Problem with generics
      ... definition in that package. ... Entities in a file with there architecture, testbench in an other with ... tried a lot of things and the "compile all" was part of it. ... But what I saw is it seems that the testbench does not recompile ...
      (comp.lang.vhdl)
    • Re: Use of libraries
      ... the entity will also contain the package that defines its interface ... 'Compile out of date' from the GUI and go right on back to simulating. ... vcom -just p *.vhd ...
      (comp.lang.vhdl)