Re: make install-javahl fails

Hey, good timing! Just last night I was reading your thread from
earlier in the week. My experience with the command-line wrapper
implementation has been really unacceptable. Earlier today I decided
to try installing the javahl interface and I was successful.

On Sat, Feb 12, 2005 at 04:49:44PM -0600, Steve Cohen wrote:
| OK, let's start fresh. I posted this earlier but in a way that may have
| been too verbose. I'm trying to install javahl with no luck onto a RH9
| system.
|
| My JAVA_HOME is /usr/local/j2sdk1.4.2. It's a Sun JDK, installed in
| /usr/local precisely because it was installed outside of the redhat RPM
| system.
|
| I've installed eclipse 3.0. It works fine with this java configuration.
|
| I've installed subversion-1.13 via src rpm (from David Summers). It
| works. This rpm does not install javahl.

Ok, so far so good. I use debian, but the concept is the same.

| I still have the BUILD directory with all the makefiles, configure
| scripts, etc.
|
| I've installed subeclipse. It works - albeit slowly.
|
| From this configuration, I can run make-javahl and it works.
| I cannot run install-javahl. It tries to install the libraries into
| /usr/local/lib producing error message from libtool:
|
| libtool: install: error: cannot install `libsvn_delta-1.la' to a
| directory not ending in /usr/lib

This is odd, I think, but it may be something with redhat's libtool.
Libraries can be installed anywhere you please. In order for the
library to be useful, it must be able to be found by the linker ('ld')
for the process that you want to use it. I'll explain this better
later on.

[...]
| How can we configure this to load javaHL under my system? It seems a
| shame to have come all this way only to fail because of an install script.

Here is what I did, and why:

    $ mkdir subclipse
    $ cd subclipse
    $ wget http://subversion.tigris.org/tarballs/subversion-1.1.3.tar.gz
    $ tar -zxvf subversion-1.1.3.tar.gz
    $ cd subversion-1.1.3

First I created a new directory to work in. I downloaded and unpacked
the source directly from the subversion team.

    $ ./configure --prefix=$HOME/opt/subversion --enable-javahl \
                --with-jdk=/usr/lib/j2sdk1.5-sun/ \
                --without-apache --without-swig
    $ make && make javahl && make install && make install-javahl

Then I configured, built and installed the software.

Some background information pertaining to my choice of paths:
    + my system is debian
    + subversion is installed from the vendor-supplied package
    + Java is a installed from a locally-built package containing the Sun JDK
        (it it just a handy mechanism debian has for this situation
         similar to their kernel package builder;
         http://packages.debian.org/unstable/misc/java-package)
    + I don't have $JAVA_HOME set; instead I just rely on $PATH to
        find the right 'java', and for any application that really
        needs $JAVA_HOME I use a shell script to set the right one for
        that application (ie some might use 1.4 while others use 1.5)
    + eclipse is installed locally in /opt
    + subclipse was installed in ~/.eclipse by eclipse' update manager
    + I did all of the javahl building and installing as a non-root user

The first key to making this work is the parameters to 'configure'.

    First I tell it where I want it to install the end result. I
    chose a dedicated directory in my home directory. This keeps it
    out of the way of the packaging system and keeps it self-contained
    so I can easily remove it when I want to (for example when I
    upgrade).

    Second I tell it where to find the java to build with. I haven't
    tried, but I suspect that the library will only work with the java
    it was compiled with. (yes, this means that I must rebuild when I
    upgrade to java 1.6)

    Third I told configure not to use any apache or swig. I don't
    know if that really matters or not, but since I already have all
    of subversion from my vendor-supplied packages I really don't need
    anything extra from this build.

    Finally, I have several "-dev" packages installed on my system. I
    don't know which one(s) other than libc6-dev that subversion needs
    when building. I just know that I didn't need any I didn't
    already have.
    
Once configure has configured the build system to do what you want,
let it run. The 'install' and 'install-javahl' targets copy the
libraries and everything needed at runtime into the directory
specified to configure's --prefix argument. Yes this builds and
installs a 'svn' and 'svnadmin', etc, that you don't need. This isn't
a problem with my choice of --prefix because they are not in my $PATH
and will never be used.

Finally, I need to enable eclipse to find the javahl library that I
now have. I already have a shell script in ~/bin (which is in my
$PATH) to run eclipse. I simply added two more lines to that script.
The script is essentially as follows :

    #!/bin/bash

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/opt/subversion/lib
    export CLASSPATH=$CLASSPATH:$HOME/opt/subversion/lib/svn-javahl/svn-javahl.jar

    exec /opt/eclipse-3.0.1/eclipse \
            -data ~/projects/eclipse \
            -vm /usr/lib/j2sdk1.5-sun/bin/java

The first key is to set $LD_LIBRARY_PATH so that the linker will be
able to find libsvnjavahl-1.so. Read the manpage for 'ld.so' for more
information on the linker and how it finds libraries.

The second key is to set $CLASSPATH so that java will find the java
portion of javahl.

Finally it runs eclipse with the necessary parameters.

I hope this information helps. If I've provided too much detail and
created additional confusion then please ask for further
clarification. (be sure to Cc me because I don't check this list very
often at all)

-D

PS Below is some more background information on C and linux
    distributions:

    A side note on -dev packages: the C and C++ build
    environments require certain files (header files) that are not
    needed at runtime. Distributions choose to provide the
    binaries and the headers separately so people who don't do any
    compiling or development don't need to install the headers.

    With a working knowledge of C's build and runtime environments and
    your OS's packaging system it would probably be fairly easy, or at
    least straightforward, to modify the spec file of the srpm you
    used so that it builds javahl and includes it in the binary rpm.

-- 
He who finds a wife finds what is good
and receives favor from the Lord.
        Proverbs 18:22
 
www: http://dman13.dyndns.org/~dman/            jabber: dman_at_dman13.dyndns.org