Well, I can add it to the Mandrake RPM set once I can get it to compile here.
Just out of curiosity, though, what files does the final javahl build encompass and what
exactly will it accomplish? lol - Sorry. I'm not familiar with the package. I'm just dealing
w/ it as a compile task to be added and a package to be built, so you'll have to ignore
my ignorance.
If you would like to suggest a comment or something, I'd be happy to immortalize
your words to be put into the description, unless someone else has a better
explanation or an objection or both. lol
Let me know. Meantime, I'm back to compiling my 0.30.0 and then gonna try the
javahl.
Any other goodies that we don't compile by default that would be nice to have added
to a set of RPMs? Feel free to tell me what other directories we don't currently
auto-decend into.
I know for one, the documentation isn't. I'm still wrangling with that.
Shamim Islam
BA BS.
lamikr_mdk (lamikr_mdk@aragorn.kortex.jyu.fi) wrote:
>
>Ok
>
>I finally got javahl builded. Biggest problem was finding the correct
>compination of aclocal, autoconf and automake. I would like to submit
>the small patch but I am not sure which are the preferred parameters for
>the diff for making patch.
>
>Here is the steps which worked with my Mandrake Linux cooker.
>
>1) I took the newest subversion version from the repository
>
>2) First I needed to build subversion (or at least configure)
> cd subversion
> autogen.sh
> ./configure --enable-maintainer-mode
> make
>
>3) Patching javahl
> cd subversion/bindings/java/javahl
> patch -p0 < patch from the url
>http://subversion.tigris.org/issues/show_bug.cgi?id=1501
>
>4) Configuring javahl
> aclocal-1.7
> autoconf-2.5x
> libtoolize --automake --force
> automake-1.7 -a
> ./configure
>
>5) fix 2 small errors from the javahl/native/Prompter.cpp
> change line 419:
>SVN_AUTH_PARAM_SSL_SERVER_FAILURES_IN, -->
>SVN_AUTH_PARAM_SSL_SERVER_FAILURES,
> change line 457: cred->failures_allow = failures_in; -->
>cred->accepted_failures = failures_in;
>
>6) build javahl
> make --> you should see libsvnjavahl.so, etc in the directory
>javahl/native/.lib
>
>Mika
>
>
>Files wrote:
>> Maybe my problem was that I was running autogen.sh instead.
>>
>> I'll try your option later tonight. Later.
>>
>> Shamim Islam
>> BA BS
>>
>> lamikr_mdk (lamikr_mdk@aragorn.kortex.jyu.fi) wrote:
>>
>>>Hi
>>>
>>>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
>>
>>>problem.
>>>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]$ aclocal-1.6
>>> [lamikr]$ WANT_AUTOCONF_2_5=1 autoconf
>>> [lamikr]$ libtoolize --automake --force
>>> [lamikr]$ automake -a
>>> [lamikr]$ ./configure
>>>
>>>After that starts problems with building
>>>First problems happens immediately with make in the src-directory where
>>>it tries to run following command
>>>
>>> CLASSPATH=../cls:./../cls:$CLASSPATH /apps/java/jdk/jdk1.4.2/bin/javac
>>>-d ../cls
>>>
>>>I think that the correct line in the src/Makefile line 123 should be
>>>something like
>>>
>>> $(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...
>>>
>>>Mika
>>>
>>>
>>>Files wrote:
>>>
>>>>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 (lamikr_mdk@aragorn.kortex.jyu.fi) wrote:
>>>>
>>>>
>>>>>Hi
>>>>>
>>>>>
>>>>> pathc -p0 <patch3
>>>>
>>>>
>>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>>>For additional commands, e-mail: dev-help@subversion.tigris.org
>>>
>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 05:36:37 2003