You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Files <fi...@poetryunlimited.com> on 2003/09/26 20:08:36 UTC
javahl patch - Mika - it won't go. Steps follow.
1. New trunk co
2. cd trunk
3. ./configure --prefix=/usr
4. cd subversion/bindings/java
5. patch -p0 < patches.txt
6. cd javahl
7. aclocal
8. WANT_AUTOCONF_2_5=1 autoconf
9. libtoolize --automake --force
10. automake -a
11. ./configure --with-jdk=/usr/java/j2sdk1.4.2_03 --prefix=/usr
12. JDK=/usr/java/j2sdk1.4.2_03 make -e
Making all in src
make[1]: Entering directory
`/tmp/subversion/trunk/subversion/bindings/java/javahl/src'
CLASSPATH=../cls:./../cls:$CLASSPATH /usr/java/j2sdk1.4.1_03/bin/javac -d ../cls
echo timestamp > class.stamp
make[1]: Leaving directory
`/tmp/subversion/trunk/subversion/bindings/java/javahl/src'
Making all in native
make[1]: Entering directory
`/tmp/subversion/trunk/subversion/bindings/java/javahl/native'
make[1]: *** No rule to make target `../cls/org/tigris/subversion/javahl/SVNClient.
class', needed by `org_tigris_subversion_javahl_SVNClient.h'. Stop.
make[1]: Leaving directory
`/tmp/subversion/trunk/subversion/bindings/java/javahl/native'
make: *** [all-recursive] Error 1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin,
Patrick - or anyone else if interested]
Posted by Patrick Mayweg <ma...@qint.de>.
Hi Branko,
Branko Čibej wrote:
>Files wrote:
>
>
>
>>Oh, man. I've been staring at these numbers too long.
>>
>>I apologize.
>>
>>I have J2SDK1.4.2 final at home and J2SDK1.4.2 release 3 (J2SDK1.4.2_03)
>>at work.
>>
>>
>>
>>
>Actually, you can't have that, either. :-) The latest release is
>1.4.2_01; you _could_ have 1.4.1_03, which was the last in the 1.4.1 series.
>
>
javahl needs only jdk 1.3 and should build with any 1.3 or 1.4 jdk.
There is nothing in there which need 1.4.
Regards,
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin,
Patrick - or anyone else if interested]
Posted by Branko Čibej <br...@xbc.nu>.
Files wrote:
>Oh, man. I've been staring at these numbers too long.
>
>I apologize.
>
>I have J2SDK1.4.2 final at home and J2SDK1.4.2 release 3 (J2SDK1.4.2_03)
>at work.
>
>
Actually, you can't have that, either. :-) The latest release is
1.4.2_01; you _could_ have 1.4.1_03, which was the last in the 1.4.1 series.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika,
Florin, Patrick - or anyone else if interested]
Posted by Files <fi...@poetryunlimited.com>.
Oh, man. I've been staring at these numbers too long.
I apologize.
I have J2SDK1.4.2 final at home and J2SDK1.4.2 release 3 (J2SDK1.4.2_03)
at work.
Ugh. So sorry. I was *so* sure it was 1.4.3. But then again, I should
have never drafted that message while I was still at work, without
checking the version numbers at home one more time.
I should have checked it again, instead of just cutting and pasting it.
You're absolutely right. J2SDK1.4.2 final is the latest release.
*sigh*
Please pass the caffeine and jolt please.
Again, I'm sorry.
Shamim Islam
BA BS
On Sat, 2003-09-27 at 00:30, Florin Iucha wrote:
> On Fri, Sep 26, 2003 at 10:52:38PM -0400, Files wrote:
> > *******************************************************
> > Florin
> > *******************************************************
> >
> > JDK 1.4.3 is out - has been for a month or more. :) You should get it.
> > Latest mozilla requires it. :-)
>
> [snip]
>
> > Florin, the latest jdk is out - 1.4.3 - get it. :)
>
> Sun's website shows JDK 1.4.2 as "NEW". Could you please post an URL
> to download JDK 1.4.3?
>
> florin
--
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl solved
Posted by Cédric Chabanois <cc...@ifrance.com>.
Yes good job !
I had myself to modify configure.in before making it work. So it seems
it was not necessary ...
Concerning subclipse, we actually support Eclipse 2.1.1 (but we may
choose soon to support Eclipse 3.0M3 if necessary)
javahl did not work with Eclipse 2.1.1 due to threading problems.
It seems to work with eclipse 3.0M3
Can someone test javahl (the one from McClain Looney) with eclipse 2.1.1
and subclipse 0.8 (mine) and tell me if it works for him ?
I hope too that javahl patch will get in this week-end.
Cédric
> Yahoo and congrats!
>
> So it worked with automake 1.6 without need to modify configure.in?
> Maybe we should write some addons/modifications to the javahl/INSTALL
> just in case that some another newbie will try to build it soon
> without first reading this thread. -:)
>
> Btw, there is finally an unofficial binary for the Linux subclipse
> plugin available in the
> http://www.loonsoft.com/downloads/svnplugin-8.0a-linux-bin.zip
>
> McClain Looney got it working yesterday. It will require eclipse 3 (I
> am testing it with eclipse 3 integration release from 25.9 2003)
>
> There is hope that both the javahl and subclipse patches will get in
> this weekend to the version control.
>
> Mika
>
> Files wrote:
>
>> On Sat, 2003-09-27 at 03:19, lamikr_mdk wrote:
>>
>>> I have followed the development in the OS/2 and there automake and
>>> autoconf have often caused problems due to filesystem having drive
>>
>>
>>
>> automake1-6 was sufficient without straying from stock Mandrake 9.1
>> packages. :-)
>>
>> Thanks so much for your help. Now all I have to do is figure out what
>> files would normally get installed, where they would go, and create an
>> RPM to go with that.
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
> _____________________________________________________________________
> Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
> http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France
>
_____________________________________________________________________
Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl solved
Posted by lamikr_mdk <la...@aragorn.kortex.jyu.fi>.
Yahoo and congrats!
So it worked with automake 1.6 without need to modify configure.in?
Maybe we should write some addons/modifications to the javahl/INSTALL
just in case that some another newbie will try to build it soon without
first reading this thread. -:)
Btw, there is finally an unofficial binary for the Linux subclipse
plugin available in the
http://www.loonsoft.com/downloads/svnplugin-8.0a-linux-bin.zip
McClain Looney got it working yesterday. It will require eclipse 3 (I am
testing it with eclipse 3 integration release from 25.9 2003)
There is hope that both the javahl and subclipse patches will get in
this weekend to the version control.
Mika
Files wrote:
> On Sat, 2003-09-27 at 03:19, lamikr_mdk wrote:
>
>>I have followed the development in the OS/2 and there automake and
>>autoconf have often caused problems due to filesystem having drive
>
>
> automake1-6 was sufficient without straying from stock Mandrake 9.1
> packages. :-)
>
> Thanks so much for your help. Now all I have to do is figure out what
> files would normally get installed, where they would go, and create an
> RPM to go with that.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl solved
Posted by Files <fi...@poetryunlimited.com>.
On Sat, 2003-09-27 at 03:19, lamikr_mdk wrote:
> I have followed the development in the OS/2 and there automake and
> autoconf have often caused problems due to filesystem having drive
automake1-6 was sufficient without straying from stock Mandrake 9.1
packages. :-)
Thanks so much for your help. Now all I have to do is figure out what
files would normally get installed, where they would go, and create an
RPM to go with that.
I'll get to that after Wednesday this week.
On another note, I have 0.30.0 compiling clean, as well as the trunk for
Mandrake RPMs.
Now, I just have to figure out what the log message should say. The
number of files in that little packaging directory have grown
significanly, if only in the interests of allowing people to use the
contents to compile 0.29.0 as well as 0.30.0 as well as the trunk with
the same toolset. lol I must be a glutton for punishment.
Later.
--
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin,
Patrick - or anyone else if interested]
Posted by lamikr_mdk <la...@aragorn.kortex.jyu.fi>.
I have followed the development in the OS/2 and there automake and
autoconf have often caused problems due to filesystem having drive
letters and not having symbolic links. I thought that after running
Linux I will not have these problems anymore but I forget the versioning
problem. :-(
Anyway if you want to build javahl with the older distro than I have
then I believe that you really must to modify configure in. Basic things
that makefiles should do are in my understanding following.
Build all java-files from the src directory.
Produce h.files from the java-classes for the native c-part.
Build c-files from the native-directory
Link c-files together
jar all java classes to single jar.
Mika
Florin Iucha wrote:
> On Sat, Sep 27, 2003 at 01:11:10AM -0400, Files wrote:
>
>>In the meantime, do you have any knowledge of the internal workings of
>>automake and the like?
>
>
> Urrgh... no! I tried approaching them and I saw people running scared :)
>
> florin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin, Patrick - or anyone else if interested]
Posted by Florin Iucha <fl...@iucha.net>.
On Sat, Sep 27, 2003 at 01:11:10AM -0400, Files wrote:
> In the meantime, do you have any knowledge of the internal workings of
> automake and the like?
Urrgh... no! I tried approaching them and I saw people running scared :)
florin
--
Don't question authority: they don't know either!
Re: javahl building woes for Mandrake RPM generation [For Mika,
Florin, Patrick - or anyone else if interested]
Posted by Files <fi...@poetryunlimited.com>.
In the meantime, do you have any knowledge of the internal workings of
automake and the like?
Thanks.
> --
> Shamim Islam
> BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin, Patrick - or anyone else if interested]
Posted by Florin Iucha <fl...@iucha.net>.
On Fri, Sep 26, 2003 at 10:52:38PM -0400, Files wrote:
> *******************************************************
> Florin
> *******************************************************
>
> JDK 1.4.3 is out - has been for a month or more. :) You should get it.
> Latest mozilla requires it. :-)
[snip]
> Florin, the latest jdk is out - 1.4.3 - get it. :)
Sun's website shows JDK 1.4.2 as "NEW". Could you please post an URL
to download JDK 1.4.3?
florin
--
Don't question authority: they don't know either!
Re: javahl building woes for Mandrake RPM generation [For
Mika, Florin, Patrick - or anyone else if interested]
Posted by Files <fi...@poetryunlimited.com>.
On Sat, 2003-09-27 at 03:08, lamikr_mdk wrote:
> > 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
I would, but I can't even find documentation on the automake-1.4.
> What version of aclocal you have?
My aclocal is in my automake package - same rev.
> 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)
I think I might have solved it though. 9.1 Bamboo also allows for
version 1.6 of automake - 1.7 is still cooker level.
So I'm going to go try that. If that fixes it, I'm home free.
Otherwise, I get to dig through historical documentation the rest of the
weekned. Ugh.
--
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl building woes for Mandrake RPM generation [For Mika, Florin,
Patrick - or anyone else if interested]
Posted by lamikr_mdk <la...@aragorn.kortex.jyu.fi>.
> 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
javahl building woes for Mandrake RPM generation [For Mika,
Florin, Patrick - or anyone else if interested]
Posted by Files <fi...@poetryunlimited.com>.
*******************************************************
Mika,
*******************************************************
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.
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)
Hope this clarifies things.
*******************************************************
Patrick.
*******************************************************
However, here's something interesting. Even if I skip the patch
altogether I see the following.
In the java tree, when I checkout files, I get CRLFs strewn about.
Since the text files should be listed as text files, shouldn't the CRLFs
be translated to LFs only?
The Makefile.am's contain CRLFs.
These CRLFs are hampering the interpretation of the Makefile.in that
results, since the trailing \ is not being honored in the resulting
Makefile after a configure run. (see the noinst_JAVA macro definition)
And lastly, the class.stamp target has an empty $(_JAVA) depndency list
in the final step just prior to calling make, which means that no source
files are compiled.
If the dependency list had been noinst_JAVA, it would have worked fine.
Question is - how is the class.stamp target generated?
If anyone knows, that would help me greatly.
So long and thanks for all the fish.
Shamim Islam
BA BS
P.S. In case anyone is wondering, all this is happening in the
subversion/bindings/java/javahl directory after doing a autogen.sh and a
configure in the main subversion directory.
*******************************************************
Florin
*******************************************************
JDK 1.4.3 is out - has been for a month or more. :) You should get it.
Latest mozilla requires it. :-)
On Fri, 2003-09-26 at 20:22, lamikr_mdk wrote:
> No I have sun JDK
>
> [lamikr@aragorn lamikr]$ java -version
> java version "1.4.2"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
> Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
>
> And the correct sequence for me requires that I am running automake-1.7,
> aclocal-1.7 and autoconf-2.5.x. Here is the whole output starting from
> the svn command and ending to the javahl build.
>
Florin, the latest jdk is out - 1.4.3 - get it. :)
> >
> > ^^
> > Is this IBM JDK?
> > I am asking because Sun's JDK is at 1.4.2_01.
> >
> > Could that be the problem?
> >
> > Cheers,
> > florin
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
--
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl patch - Mika - it won't go. Steps follow.
Posted by lamikr_mdk <la...@aragorn.kortex.jyu.fi>.
No I have sun JDK
[lamikr@aragorn lamikr]$ java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
And the correct sequence for me requires that I am running automake-1.7,
aclocal-1.7 and autoconf-2.5.x. Here is the whole output starting from
the svn command and ending to the javahl build.
1) get subversion
- [lamikr@aragorn subversion]$ svn co
http://svn.collab.net/repos/svn/trunk subversion
2) build subversion
- cd subversion
- autogen.sh
- ./configure
- make
3) patch javahl
cd subversion/bindings/java
patch -p0 < patch.txt (patch downloaded from the subversion issue
attachment 1501)
4) build javahl
- cd javahl
- aclocal-1.7
- autoconf-2.5x
- libtoolize --automake --force
- automake-1.7 -a
- ./configure
- make
Note! If I tried to configure javahl by calling things like
"aclocal-1.6, WANT_AUTOCONF_2_5=1 autoconf or ,,, then the generation of
makefiles did not work for me.
So the correct sequence is for me (It is important to run it into javahl
environment where you have not made any configuration changes or
commands earlies)
0. make sure that /usr/java/j2sdk1.4.2_03/bin is in your path. Test with
"java -version"
1. New trunk co
2. cd trunk
3. ./autogen.sh
4. ./configure --prefix=/usr
5. make
5. cd subversion/bindings/java
6. patch -p0 < patches.txt
7. cd javahl
8. aclocal-1.7
9. autoconf-2.5x
10. libtoolize --automake --force
11. automake-1.7 -a
12. ./configure
13. make
Mika
the erronous (just one combination of many) is
[lamikr@aragorn subversion]$ WANT_AUTOCONF_2_5=1 autoconf
[lamikr@aragorn subversion]$ libtoolize --automake --force
[lamikr@aragorn subversion]$ automake -a
configure.in: 74: `automake requires `AM_CONFIG_HEADER', not
`AC_CONFIG_HEADER'
automake: configure.in: `PACKAGE' not defined in `configure.in'
automake: configure.in: installing `ac-helpers/mkinstalldirs'
automake: configure.in: installing `ac-helpers/missing'
automake: .am: `install.sh' is an anachronism; use `install-sh' instead
automake: no `Makefile.am' found or specified
Mika
Florin Iucha wrote:
> On Fri, Sep 26, 2003 at 08:08:8. aclocal-1.7
9. autoconf-2.5x
10. libtoolize --automake --force
11. automake-1.7 -a
12. ./configure
13. make 36PM +0000, Files wrote:
>
>>1. New trunk co
>>2. cd trunk
>>3. ./configure --prefix=/usr
>>4. cd subversion/bindings/java
>>5. patch -p0 < patches.txt
>>6. cd javahl
>>7. aclocal
>>8. WANT_AUTOCONF_2_5=1 autoconf
>>9. libtoolize --automake --force
>>10. automake -a
>>11. ./configure --with-jdk=/usr/java/j2sdk1.4.2_03 --prefix=/usr
>>12. JDK=/usr/java/j2sdk1.4.2_03 make -e
>
> ^^
> Is this IBM JDK?
> I am asking because Sun's JDK is at 1.4.2_01.
>
> Could that be the problem?
>
> Cheers,
> florin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: javahl patch - Mika - it won't go. Steps follow.
Posted by Florin Iucha <fl...@iucha.net>.
On Fri, Sep 26, 2003 at 08:08:36PM +0000, Files wrote:
> 1. New trunk co
> 2. cd trunk
> 3. ./configure --prefix=/usr
> 4. cd subversion/bindings/java
> 5. patch -p0 < patches.txt
> 6. cd javahl
> 7. aclocal
> 8. WANT_AUTOCONF_2_5=1 autoconf
> 9. libtoolize --automake --force
> 10. automake -a
> 11. ./configure --with-jdk=/usr/java/j2sdk1.4.2_03 --prefix=/usr
> 12. JDK=/usr/java/j2sdk1.4.2_03 make -e
^^
Is this IBM JDK?
I am asking because Sun's JDK is at 1.4.2_01.
Could that be the problem?
Cheers,
florin
--
Don't question authority: they don't know either!