[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

javahl building woes for Mandrake RPM generation [For Mika, Florin, Patrick - or anyone else if interested]

From: Files <files_at_poetryunlimited.com>
Date: 2003-09-27 04:52:38 CEST

*******************************************************
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
Received on Sat Sep 27 04:53:20 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.