> I'm not having trouble where you think I am. The version issue is not
> the issue. Unless you're telling me that the target generation for 1.4
> is flawed in which case all of subversion should fail spooktacularly.
>
> I can't do a standard RPM/SRPM for Mandrake 9.1 if I have to be at
> cooker to get it to even compile.
Ok now I understand. Your problem is basically happening because you
want to use older versions of aclocal, autoconf and automake than I
have. (or works out of the box with the current javahl)
I think that then you relly need to try to find out how aclocal,
autoconf and automake are really working and try to make fixes to
configure.in in order to get it working also with the older version of
these.
> Other than that, I have:
>
> automake-1.4-21.p6.mdk
> autoconf2.5-2.57-3mdk
> J2SDK1.4.3 at home, J2SDK1.4.2_03 at work.
> make-3.80-3mdk
> Mandrake 9.1 (Bamboo)
What version of aclocal you have?
If I try to run older versions of these tools I will also get problems.
One example run with the problematic environment is: (calling aclocal
instead than aclocal-1.7 and automake-1.4 instead than automake-1.7)
[lamikr@aragorn javahl]$ aclocal
[lamikr@aragorn javahl]$ autoconf-2.5x
[lamikr@aragorn javahl]$ libtoolize --automa
[lamikr@aragorn javahl]$ libtoolize --automake --force
[lamikr@aragorn javahl]$ automake-1.4 -a
[lamikr@aragorn javahl]$ ./configure
creating config.nice
checking for a BSD-compatible install... /usr//bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... found
checking for working autoconf... found
checking for working automake-1.4... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a BSD-compatible install... /usr//bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ld used by GCC... /usr//bin/ld
checking if the linker (/usr//bin/ld) is GNU ld... yes
checking for /usr//bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr//bin/nm -B
checking for a sed that does not truncate output... /bin/sed
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking command to parse /usr//bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr//bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for JDK... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating native/Makefile
config.status: creating cls/Makefile
config.status: creating doc/Makefile
[lamikr@aragorn javahl]$ make
Making all in src
make[1]: Entering directory
`/home/lamikr/downloads/subversion/subversion/subversion/bindings/java/javahl/src'
CLASSPATH=../cls:./../cls:$CLASSPATH /apps/java/jdk/jdk1.4.2/bin/javac
-d ../cls
javac: no source files
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is
doing
-deprecation Output source locations where deprecated
APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified
release
-target <release> Generate class files for specific VM version
-help Print a synopsis of standard options
make[1]: *** [class.stamp] Error 2
make[1]: Leaving directory
`/home/lamikr/downloads/subversion/subversion/subversion/bindings/java/javahl/src'
make: *** [all-recursive] Error 1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Sep 27 09:09:23 2003