1.7 neon fetched by get-deps.sh, but not usable by configure?

tsteven four

unread,

Jul 29, 2011, 10:25:15 AM7/29/11

to us...@subversion.apache.org

get-deps.sh fetches neon 0.29.6, but configure reports:

configure: checking neon library
checking for neon-config... no

An appropriate version of neon could not be found, so libsvn_ra_neon
will not be built. If you want to build libsvn_ra_neon, please
install neon 0.29.6 on this system.

no suitable neon found

I understand serf is now the default but I expected neon to still be built.
Is this a bug or is some configure option now necessary to use the neon
downloaded by get-deps?

Mark Phippard

unread,

Jul 29, 2011, 10:28:26 AM7/29/11

to tsteven four, us...@subversion.apache.org

Did you build Neon? AFAIK, get-deps.sh just downloads the source code, it does not build it and neither does the Subversion build process. configure is saying it does not find an installed Neon. So you need to run configure and make install for Neon first.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

Mark Phippard

unread,

Jul 29, 2011, 10:45:27 AM7/29/11

to tsteven four, us...@subversion.apache.org

Please reply to users@ list.

On Fri, Jul 29, 2011 at 10:39 AM, tsteven four <tste...@gmail.com> wrote:

No, I did not build neon, but with 1.6 configure would build the makefile and neon would be listed in SVN_EXTERNAL_PROJECT_SUBDIRS. then when subversion was made, the dependencies listed in SVN_EXTERNAL_PROJECT_SUBDIRS would get made, including neon. So the subversion build process used to build neon (and possibly apr, apr-util, apr_memcache, serf), but it appears incapable of building neon with 1.7. If the intent is to no longer provide build support for neon, perhaps get-deps.sh should not download it and instead print a message "If you require neon, the recommended version is ..." as it does with apr-iconv and httpd. To me this would suggest to the builder that you are now on your own with neon.

I am not aware of the build process working that way. I will take your word for it, but I have always had to build components. I recall in the early 1.x days that the build process would build dependencies if they were located within the source tree, but I thought that was all removed by at least 1.5, and maybe even 1.4. I know this, because to this day, I still cannot figure out how to build APR easily. I always wind up building httpd instead and then pointing at its build of APR.

Anyway, I was not giving you an answer as an expert on the topic. Was just trying to help based on my own experiences and what the error message was saying.

Jeremy Whitlock

unread,

Oct 9, 2011, 12:16:09 AM10/9/11

to Mark Phippard, tsteven four, us...@subversion.apache.org

Hello all,
I can confirm that Neon use to be built automatically by
Subversion without specifying --with-neon if the Neon sources were
within the Subversion sources directory. As of 1.7.0, this is no
longer the case and I am now having to manually build/install Neon and
then use the --with-neon configure flag. It's not a big deal but I
too was surprised by this.