You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mo DeJong <md...@cygnus.com> on 2001/02/11 23:02:52 UTC
Problem building with neon 0.11.0
I just tried to build subversion with neon 0.11.0
and ran into a little problem.
% ./autogen.sh
...
...Uh oh, there is a problem.
You have a neon/ subdir, but it is not neon 0.11.0.
Please get neon 0.11.0 from:
http://www.webdav.org/neon/neon-0.11.0.tar.gz
It seems the check in autogen.sh is not working
because neon has changed the way it declares
the version number. It is no longer possible
to grep the configure.in file to get the
version number.
aclocal.m4:NEON_VERSION_MAJOR=0
aclocal.m4:NEON_VERSION_MINOR=11
aclocal.m4:NEON_VERSION_RELEASE=0
aclocal.m4:NEON_VERSION_TAG=
aclocal.m4:NEON_VERSION="${NEON_VERSION_MAJOR}.${NEON_VERSION_MINOR}.${NEON_VERS
ION_RELEASE}${NEON_VERSION_TAG}"
So, I wrote up this little patch to fix things.
Index: autogen.sh
===================================================================
RCS file: /cvs/subversion/autogen.sh,v
retrieving revision 1.31
diff -u -r1.31 autogen.sh
--- autogen.sh 2001/02/05 03:06:34 1.31
+++ autogen.sh 2001/02/11 22:58:33
@@ -57,7 +56,12 @@
fi
# Handle the neon/ subdir
-NEON_VER=0.8.1
+NEON_VERSION_MAJOR=0
+NEON_VERSION_MINOR=11
+NEON_VERSION_RELEASE=0
+NEON_VERSION_TAG=
+NEON_VER="${NEON_VERSION_MAJOR}.${NEON_VERSION_MINOR}.${NEON_VERSION_RELEASE}${NEON_VERSION_TAG}"
+
if [ ! -d neon ]; then
echo ""
echo "...Uh oh, there is a problem."
@@ -69,9 +73,31 @@
echo "directory from ./neon-${NEON_VER}/ to ./neon/"
echo ""
exit 1
+fi
+
+error=0
+
+grep NEON_VERSION_MAJOR=${NEON_VERSION_MAJOR} neon/macros/neon.m4 > /dev/null
+if [ $? -ne 0 ]; then
+ error=1
+fi
+
+grep NEON_VERSION_MINOR=${NEON_VERSION_MINOR} neon/macros/neon.m4 > /dev/null
+if [ $? -ne 0 ]; then
+ error=1
fi
-grep NEON_VERSION=${NEON_VER} neon/configure.in > /dev/null
+
+grep NEON_VERSION_RELEASE=${NEON_VERSION_RELEASE} neon/macros/neon.m4 > /dev/null
if [ $? -ne 0 ]; then
+ error=1
+fi
+
+grep NEON_VERSION_TAG=${NEON_VERSION_TAG} neon/macros/neon.m4 > /dev/null
+if [ $? -ne 0 ]; then
+ error=1
+fi
+
+if [ $error -ne 0 ]; then
echo ""
echo "...Uh oh, there is a problem."
echo "You have a neon/ subdir, but it is not neon ${NEON_VER}."
Mo DeJong
Red Hat Inc
Re: Problem building with neon 0.11.0
Posted by Greg Stein <gs...@lyra.org>.
On Sat, Feb 17, 2001 at 08:56:24PM -0500, Kevin Pilch-Bisson wrote:
> On Sat, Feb 17, 2001 at 05:49:19PM -0800, Mo DeJong wrote:
> > Cool, it builds now.
> >
> > Big thanks to gstein and joe for fixing
> > things up, I can now compile subversion
> > with neon 0.11.0 when builddir != srcdir.
> >
> > This is a minor nit, but did does
> > automake need --foreign to avoid this eror?
> > Passing --gnu seems to be incorrect since
> > there are no ChangeLogs.
> >
> > % cd ~/project/build/subversion
> > % make clean
> > cd /home/mo/project/subversion && aclocal -I ac-helpers
> > cd /home/mo/project/subversion && automake --gnu Makefile
> > automake: Makefile.am: required file `./ChangeLog' not found
> > make: *** [/home/mo/project/subversion/Makefile.in] Error 1
>
> There is a rulr for subversion to make the ChangeLog from cvs log in the
> Makefile. The problem is that it doesn't work if you aren't in the CVS
> directory. This is something I noticed, but didn't really look into too
> deeply when I was previously working on trying to get builddir != srcdir
> builds working. The cvs2cl.pl script is what is used. I haven't really
> looked at it, but I will take a look now, and see if there is a way to
> get it to work. The problem is that the ChangeLog should be created in
> the srcdir (since that is where it belongs), but technically, nothing in
> the build process should modify anything in srcdir. It should be
> possible for srcdir to be on a readonly file system. Maybe we should
> skip that technicality for subversion? What do people think?
>...
I say that we just skip the creation of the ChangeLog. It isn't important to
end users. Look at any of our CVS checkin messages -- they aren't useful to
users.
Normally, I just "touch ChangeLog" to skip over that part.
It would be nicer to just avoid the whole "ChangeLog required" bit. If
--foreign will do that... great. +1
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: Problem building with neon 0.11.0
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
On Sat, Feb 17, 2001 at 05:49:19PM -0800, Mo DeJong wrote:
> Cool, it builds now.
>
> Big thanks to gstein and joe for fixing
> things up, I can now compile subversion
> with neon 0.11.0 when builddir != srcdir.
>
> This is a minor nit, but did does
> automake need --foreign to avoid this eror?
> Passing --gnu seems to be incorrect since
> there are no ChangeLogs.
>
> % cd ~/project/build/subversion
> % make clean
> cd /home/mo/project/subversion && aclocal -I ac-helpers
> cd /home/mo/project/subversion && automake --gnu Makefile
> automake: Makefile.am: required file `./ChangeLog' not found
> make: *** [/home/mo/project/subversion/Makefile.in] Error 1
There is a rulr for subversion to make the ChangeLog from cvs log in the
Makefile. The problem is that it doesn't work if you aren't in the CVS
directory. This is something I noticed, but didn't really look into too
deeply when I was previously working on trying to get builddir != srcdir
builds working. The cvs2cl.pl script is what is used. I haven't really
looked at it, but I will take a look now, and see if there is a way to
get it to work. The problem is that the ChangeLog should be created in
the srcdir (since that is where it belongs), but technically, nothing in
the build process should modify anything in srcdir. It should be
possible for srcdir to be on a readonly file system. Maybe we should
skip that technicality for subversion? What do people think?
>
> Mo DeJong
> Red Hat Inc
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: Problem building with neon 0.11.0
Posted by Joe Orton <jo...@manyfish.co.uk>.
On Mon, Feb 12, 2001 at 12:30:25AM +0100, Branko �ibej wrote:
> Mo DeJong wrote:
>
> > I just tried to build subversion with neon 0.11.0
>
> This won't work without some changes in the SVN code, anyway. The
> interfaces in neon have changes quite a bit. And I think we have to use
> current expat if we upgrade to current neon.
No, I haven't even integrated Sam's patches to add expat 2 support yet,
and when I do expat 2 will never be required; libxml and expat 1 support
will stay.
Regards,
joe
Re: Problem building with neon 0.11.0
Posted by Greg Stein <gs...@lyra.org>.
On Mon, Feb 12, 2001 at 12:30:25AM +0100, Branko �ibej wrote:
> Mo DeJong wrote:
>
> > I just tried to build subversion with neon 0.11.0
>
> This won't work without some changes in the SVN code, anyway. The
> interfaces in neon have changes quite a bit. And I think we have to use
> current expat if we upgrade to current neon.
It should still work against the old Expat (there is some autoconf to detect
old expats). If not, then we just beat on Joe a bit :-)
But yes: there may need to be some code changes in libsvn_ra_dav.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: Problem building with neon 0.11.0
Posted by Mo DeJong <md...@cygnus.com>.
Cool, it builds now.
Big thanks to gstein and joe for fixing
things up, I can now compile subversion
with neon 0.11.0 when builddir != srcdir.
This is a minor nit, but did does
automake need --foreign to avoid this eror?
Passing --gnu seems to be incorrect since
there are no ChangeLogs.
% cd ~/project/build/subversion
% make clean
cd /home/mo/project/subversion && aclocal -I ac-helpers
cd /home/mo/project/subversion && automake --gnu Makefile
automake: Makefile.am: required file `./ChangeLog' not found
make: *** [/home/mo/project/subversion/Makefile.in] Error 1
Mo DeJong
Red Hat Inc
Re: Problem building with neon 0.11.0
Posted by Branko Čibej <br...@xbc.nu>.
Mo DeJong wrote:
> I just tried to build subversion with neon 0.11.0
This won't work without some changes in the SVN code, anyway. The
interfaces in neon have changes quite a bit. And I think we have to use
current expat if we upgrade to current neon.
It's on the todo list; GregS has been threatening to switch for such a
looong time now. :-)
> +error=0
> +
> +grep NEON_VERSION_MAJOR=${NEON_VERSION_MAJOR} neon/macros/neon.m4 > /dev/null
> +if [ $? -ne 0 ]; then
> + error=1
> +fi
> +
> +grep NEON_VERSION_MINOR=${NEON_VERSION_MINOR} neon/macros/neon.m4 > /dev/null
> +if [ $? -ne 0 ]; then
> + error=1
> fi
> -grep NEON_VERSION=${NEON_VER} neon/configure.in > /dev/null
> +
> +grep NEON_VERSION_RELEASE=${NEON_VERSION_RELEASE} neon/macros/neon.m4 > /dev/null
> if [ $? -ne 0 ]; then
> + error=1
> +fi
> +
> +grep NEON_VERSION_TAG=${NEON_VERSION_TAG} neon/macros/neon.m4 > /dev/null
> +if [ $? -ne 0 ]; then
> + error=1
> +fi
What, keep on grepping after an error? You can't be serious. :-)
--
Brane �ibej
home: <br...@xbc.nu> http://www.xbc.nu/brane/
work: <br...@hermes.si> http://www.hermes-softlab.com/
ACM: <br...@acm.org> http://www.acm.org/
Re: Problem building with neon 0.11.0
Posted by Greg Stein <gs...@lyra.org>.
On Sun, Feb 11, 2001 at 03:02:52PM -0800, Mo DeJong wrote:
> I just tried to build subversion with neon 0.11.0
> and ran into a little problem.
It should be easier to build against 0.11.0. Have you discovered any other
build issues?
(a checkout should still work against arbitrary DAV servers, but commits are
hopelessly broken until the FS comes up to speed)
RSN, checkouts will break against regular DAV servers because I've got to
put in fetching of the DeltaV (and some SVN) information. That will leave us
to running against mod_dav_svn, which is (again) broken due to no FS.
(sigh)
Anyhow, my point is simply that we may as well upgrade to 0.11.0 soon
because we can't break things any more than they are :-)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/