javahl build strangeness

[McClain Looney <m...@loonsoft.com>]

Hello,

Has anyone else experienced strangeness with the javac invocation in the 
javahl build on debian?

after running autogen, then configure --with-jdk=$JAVA_HOME, issuing a make 
results in:


make[1]: Entering directory 
`/home/mml/subversion-1.0.1/subversion/bindings/java/javahl/src'
CLASSPATH=../cls:./../cls:$CLASSPATH /usr/local/java2/bin/javac -d ../cls
javac: no source files
Usage: javac <options> <source files>
<snip>

the relevant Makefile line is below:


class.stamp: $(_JAVA)
    132     $(CLASSPATH_ENV) $(JAVAC) -d $(JAVAROOT) $(JAVACFLAGS) $?
    133     echo timestamp > class.stamp


if i change 132 to:
$(CLASSPATH_ENV) find . -name \*.java | xargs $(JAVAC) -d $(JAVAROOT) 
$(JAVACFLAGS) $?


things work fine. strangely, this isn't an issue on osx, where the following 
is generated in the makefile:


    136 classnoinst.stamp: $(noinst_JAVA)
    137     @if test -n "$?"; then \
    138       echo '$(CLASSPATH_ENV) $(JAVAC) -d $(JAVAROOT) $(AM_JAVACFLAGS) 
$(JAVACFLAGS) $?' ; \
    139       $(CLASSPATH_ENV) $(JAVAC) -d $(JAVAROOT) \
    140         $(AM_JAVACFLAGS) $(JAVACFLAGS) $?; \
    141     else :; fi
    142     echo timestamp > classnoinst.stamp


could this be some local config issue?


-- 
McClain Looney
LoonSoft LLC
m@loonsoft.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: javahl build strangeness

["Daniel L. Rall" <dl...@collab.net>]

Patrick Mayweg wrote:
> Hi McLain,
> McClain Looney wrote:
> 
>> Hello,
>>
>> Has anyone else experienced strangeness with the javac invocation in 
>> the javahl build on debian?
>>
>> after running autogen, then configure --with-jdk=$JAVA_HOME, issuing a 
>> make results in:
>>  
>>
> While we still have the seperated build for javahl in the 1.0.x 
> brancher, it is important to use automake 1.6 or higher. If I would know 
> a way to automaticly test that during autogen.sh, I would add that.
> On trunk you should use the integrated build.

Patrick, something like what build/ac-macros/swig.m4 file does would be 
appropriate:

   if test "$SWIG" != "none"; then
     AC_MSG_CHECKING([swig version])
     SWIG_VERSION_RAW="`$SWIG -version 2>&1 | \
                        sed -ne 's/^.*Version \(.*\)$/\1/p'`"
     # We want the version as an integer so we can test against
     # which version we're using.  SWIG doesn't provide this
     # to us so we have to come up with it on our own.
     # The major is passed straight through,
     # the minor is zero padded to two places,
     # and the patch level is zero padded to three places.
     # e.g. 1.3.21 becomes 103021
     SWIG_VERSION="`echo \"$SWIG_VERSION_RAW\" | \
                   sed -e 's/[[^0-9\.]].*$//' \
                       -e 's/\.\([[0-9]]\)$/.0\1/' \
                       -e 's/\.\([[0-9]][[0-9]]\)$/.0\1/' \
                       -e 's/\.\([[0-9]]\)\./0\1/; s/\.//g;'`"
     AC_MSG_RESULT([$SWIG_VERSION_RAW])
     AC_SUBST(SWIG_VERSION)
     # If you change the required swig version number, don't forget to update:
     #   subversion/bindings/swig/INSTALL
     #   subversion/bindings/swig/README
     #   packages/rpm/mandrake-9.0/subversion.spec
     #   packages/rpm/redhat-7.x/subversion.spec
     #   packages/rpm/redhat-8.x/subversion.spec
     if test -n "$SWIG_VERSION" && test "$SWIG_VERSION" -ge "103019"; then
         SWIG_SUITABLE=yes
         ...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: javahl build strangeness

[Patrick Mayweg <ma...@qint.de>]

Hi McLain,
McClain Looney wrote:

>Hello,
>
>Has anyone else experienced strangeness with the javac invocation in the 
>javahl build on debian?
>
>after running autogen, then configure --with-jdk=$JAVA_HOME, issuing a make 
>results in:
>  
>
While we still have the seperated build for javahl in the 1.0.x 
brancher, it is important to use automake 1.6 or higher. If I would know 
a way to automaticly test that during autogen.sh, I would add that.
On trunk you should use the integrated build.

>
>make[1]: Entering directory 
>`/home/mml/subversion-1.0.1/subversion/bindings/java/javahl/src'
>CLASSPATH=../cls:./../cls:$CLASSPATH /usr/local/java2/bin/javac -d ../cls
>javac: no source files
>Usage: javac <options> <source files>
><snip>
>
>  
>
Reagrds,
Patrick


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org