Now I was able to patch it succesfully also. Last time I took the patch
from the mail, not from the the 1509 bug url, so maybe that was the
Which editor you use for seeing ctrl-m characters in the configure? I
tested with anjuta, gedit, joe and nano and everything seemed to be ok
in the configure for me.
Anyway after patching I ran following commands succesfully
[lamikr]$ WANT_AUTOCONF_2_5=1 autoconf
[lamikr]$ libtoolize --automake --force
[lamikr]$ automake -a
After that starts problems with building
First problems happens immediately with make in the src-directory where
it tries to run following command
I think that the correct line in the src/Makefile line 123 should be
$(CLASSPATH_ENV) $(JAVAC) org/tigris/subversion/javahl/*.java -d
$(JAVAROOT) $(JAVACFLAGS) $?
After that I get some problems with the build targets but I will
investigate them tomorrow...
> Hi there. Mika and Michael ( from your bug report about patch < patchfile in issue
> 1501 )
> I just tried it on the trunk. Works fine.
> cd subversion/bindings/java/javahl
> patch -p0 < patchfile_goes_here
> Everything patches successfully.
> However, after running autogen.sh, I *have* noticed that configure
> contains spurious ctrl-m characters.
> Removing these provides a working configure on linux.
> However, attempting to RUN said configure claims that install-sh and/or
> install.sh are not available.
> The first error here is the -f test instead of the -e test.
> I had to change it from test -f file to [ -e file ].
> Secondly, it complains that ls -t is broken. I think some work needs to be done on
> either the autogen.sh configuration files in this directory, or on configure.in.
> I could not at first blush figure out why the ctrl-m characters appeared in the
> first place.
> Anyway. There's a start.
> Shamim Islam
> BA BS
> lamikr_mdk (firstname.lastname@example.org) wrote:
>> pathc -p0 <patch3
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Sep 23 22:49:42 2003