Re: Re: Newbie's same old question about Cygwin (was: Re: Newbie's same old ques

Marcos Chaves wrote:
> Hi Christian.
>
>>> Cygwin source package and ./configure + make worked great as expected.
>>
>> Did you apply the patch file which comes with the source package of
>> subversion?
>>
>> Christian
>
> No, I just downloaded the 1.0.5 tarball using Cygwin's setup (when
> installed, the tarball goes to /usr/src) and then compiled it with
> ./configure + make.
>
> Which patch file is that?

The one that unpacks to /usr/src/subversion-1.0.5-1.patch when you install
the source.

Mostly it's just backports from trunk/1.1.x. Ignore it if you are building
either trunk or 1.1.x .

> Is this the one to make apr-util understand 4.2?

No.

> The apr-util version that comes with th Cygwin 1.0.5 source tarball is
> already patched and has some other changes (maybe to make it work with
> Cygwin? Mark?) and it just works.

???

No, the subversion-1.0.5.tar.bz2 that comes in the Cygwin package is the
exact unmodified official release tarball. *All* the cygwin-specific stuff
is contained in the patch file and the build script.

> The only non-trivial change (at least for me, because I still don't
> understand the reason) that I did was to create the following link so
> autogen.sh could find libtool:
>
> ln -s /usr/autotool/stable/share/aclocal/libtool.m4 /usr/share/aclocal

Don't do that! Use the *devel* not *stable* versions of the autotools.

Although the devel/stable terms were originally accurate, now:

devel = up-to-date and working well
stable = truly ancient and lacking important fixes

If you have a look in the build script (installed into /usr/src) you will
see

PATH="/usr/autotool/devel/bin:$PATH" ./autogen.sh

which accomplishes the same thing.

In fact, I have that PATH set up permanently in my user environment - these
days, its rare indeed to find a package requiring the old autoconf 2.13 and
associated other autotools.

> Anyway, I did it when I was trying to build Subversion from trunk/ and I
> don't know if it is required if you are just building from a tarball.

FWIW, I clean-build svn from trunk about once a week, with the following
commands:

./autogen.sh
./configure --disable-static
make
make install

Although, I do tend to have several patches applied to my system libtool. I
don't think any of them are required, though.

Try executing exactly the following:

export PATH="/usr/autotool/devel/bin:$PATH"
svn co http://svn.collab.net/repos/svn/trunk svn-trunk
cd svn-trunk
./autogen.sh
./configure --disable-static --prefix=/newtestsvn
make
make install

I'm running that right now (with my libtool modifications deactivated), and
I expect it to succeed. I'll post if it doesn't.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 25 23:07:53 2004