You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Neels Janosch Hofmeyr <ne...@elego.de> on 2008/02/02 21:15:06 UTC
--with-neon=DIR doesn't work
Hi dev,
I have tried to compile subversion on a FreeBSD without a system wide
neon installation. Thus, I found that it makes no sense to supply the
--with-neon option:
~/trunk $ ./configure --with-neon=../neon-0.27.2 [...and other
options, see below...]
This does not have the desired effect. configure complains with "no
suitable neon found" but keeps on running.
(about the keeping on running:
http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=112925 )
The real problem is that --with-neon seems to obstruct the build
process, regardless.
The only case that works is
~/trunk/neon
~/trunk/
./configure (omitting the --with-neon option completely)
All of the following structures fail:
1)
~/neon-0.27.2
~/trunk/
./configure --with-neon=../neon-0.27.2
2)
~/neon
~/trunk/
./configure --with-neon=../neon
3)
~/trunk/neon-0.27.2
~/trunk/
./configure --with-neon=./neon-0.27.2
and, worst of all,
4)
~/trunk/neon
~/trunk/
./configure --with-neon=./neon
Also, this doesn't work, as configure complains that --with-neon needs
an argument:
5)
~/trunk/neon (renamed directory)
~/trunk/
./configure --with-neon
So, either the --with-neon option needs to be changed to a boolean
option, or it needs to be fixed so that the argument actually has an
effect. I was almost going to be confused when I issued a
--with-neon=./neon as described by the neon error message, and still
found it complaining. Only after I dropped the --with-neon completely
did anything work out.
If someone can't reproduce this, here is the complete configure
command that I used:
./configure --disable-shared --enable-maintainer-mode
--prefix=${MY_PREFIX} --with-serf=../serf-0.1.2
--with-apache=${APACHE_SRC}
--with-apache-libexecdir=${APACHE_LIBEXECDIR} --with-neon=../neon-0.27.2
Interestingly enough, the --with-serf=../serf-0.1.2 seems to work fine.
I'd like to file this as an issue... so, do I wait for a buddy now?
Thanks,
Neels
--
Neels Janosch Hofmeyr
Software Developer
neels@elego.de
Public Key: http://binarchy.net/neels/neels.hofmeyr.public.key.asc
elego Software Solutions GmbH http://www.elegosoft.com
Gustav-Meyer-Allee 25, Gebäude 12 HRB 77719
13355 Berlin, Germany Amtsgericht Charlottenburg
Tel.: +49 30 23 45 86 96 Sitz der Gesellschaft: Berlin
Fax: +49 30 23 45 86 95 Geschäftsführer: Olaf Wagner
Re: --with-neon=DIR doesn't work
Posted by Karl Fogel <kf...@red-bean.com>.
Neels Janosch Hofmeyr <ne...@elego.de> writes:
> Basically, the only thing that really needs to be changed is the
> online help for the --with-neon option (as in configure --help). There
> would still be inconsistency (the two mentioned options work entirely
> differently, although they look similar), but I guess that's just the
> way it is, then.
>
> Still, thanks for the plus-one! Do I still file an issue to change the
> help information, or do I just send a patch?
Thanks for the clear explanation -- just posting a patch is fine, I
don't think we need an issue for this one.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: --with-neon=DIR doesn't work
Posted by Neels Janosch Hofmeyr <ne...@elego.de>.
Karl Fogel wrote:
> Neels Janosch Hofmeyr <ne...@elego.de> writes:
>
>> I have tried to compile subversion on a FreeBSD without a system wide
>> neon installation. Thus, I found that it makes no sense to supply the
>> --with-neon option:
>>
>> [...]
>>
>> I'd like to file this as an issue... so, do I wait for a buddy now?
>>
>
> I don't have time to look into this right now, but it seems like
> you've gathered a lot of details on the problem, so +1 on filing an
> issue if there isn't one already. (Please point back to this thread
> from the issue.)
>
Well, stsp and I found out the reason why --with-neon wasn't accepting
source trees, because it is supposed to accept an *installed* neon
location. To use neon sources, one does not use --with-neon, but put the
neon sources in the trunk's root directory.
The problem that remains is that this detail is not given in the online
help. While the comparable option --with-serf accepts a source
directory, --with-neon accepts only a built and installed neon. So,
someone who used --with-serf will be confused by --with-neon,
particularly since they are competing libraries for the same functionality.
Basically, the only thing that really needs to be changed is the online
help for the --with-neon option (as in configure --help). There would
still be inconsistency (the two mentioned options work entirely
differently, although they look similar), but I guess that's just the
way it is, then.
Still, thanks for the plus-one! Do I still file an issue to change the
help information, or do I just send a patch?
Thanks,
Neels
--
Neels Janosch Hofmeyr
Software Developer
neels@elego.de
Public Key at
subkeys.pgp.net
or
http://binarchy.net/neels/neels.hofmeyr.public.key.asc
elego Software Solutions GmbH http://www.elegosoft.com
Gustav-Meyer-Allee 25, Gebäude 12 HRB 77719
13355 Berlin, Germany Amtsgericht Charlottenburg
Tel.: +49 30 23 45 86 96 Sitz der Gesellschaft: Berlin
Fax: +49 30 23 45 86 95 Geschäftsführer: Olaf Wagner
Re: --with-neon=DIR doesn't work
Posted by Karl Fogel <kf...@red-bean.com>.
Neels Janosch Hofmeyr <ne...@elego.de> writes:
> I have tried to compile subversion on a FreeBSD without a system wide
> neon installation. Thus, I found that it makes no sense to supply the
> --with-neon option:
>
> [...]
>
> I'd like to file this as an issue... so, do I wait for a buddy now?
I don't have time to look into this right now, but it seems like
you've gathered a lot of details on the problem, so +1 on filing an
issue if there isn't one already. (Please point back to this thread
from the issue.)
Best,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org