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

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

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 29 Jul 2011 10:45:27 -0400

Please reply to users@ list.

On Fri, Jul 29, 2011 at 10:39 AM, tsteven four <tsteven4_at_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.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2011-07-29 16:46:00 CEST

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