Dennis Newbold <dennisn@pe.net> writes:
> I originally sent the email below to users@subversion.tigris.org on
> 6/5/2004. As of today (6/21/2004), no one has responded to me privately,
> and it has not appeared in the mailing list archives. Therefore, I am
> sending it to your list in the hope that your list admin will be a little
> more polite or effective.
There's nothing not "polite" about a failure to respond; it may just
mean no one felt they had anything helpful to say. (If you'd like the
names of some people who can provide *paid* tech support, ask me
privately :-) .)
> 2. an open source project which cannot be built "out of the box" from
> sources but instead requires special knowledge / insight into how
> everything fits -- well, it doesn't seem to be all that "open".
> I would thus suggest that the build process itself needs to be made
> cleaner and simpler, and this effort (at least in the current state
> of things) is probably best done by a developer.
One person having trouble does not mean the project's build system is
broken. It could mean that that one person did something wrong (see
below), or that some other exceptional circumstance applies.
I'm not saying Subversion is perfect, but please don't make
generalizations about it based on how frustrated you happen to feel
right now. Many non-developers have successfully installed it.
Now, about your problem:
> For various reasons, I am attempting to build subversion 1.0.4
> from the sources. I'm on a FreeBSD system. Output from config.guess
> is: i386-unknown-freebsd4.8
>
> I first ran: sh autogen.sh, and got a few warning messages, but no show-
> soppers, AFAIK. Output is in run_autogen.sh.log
Hmm, why did you run 'autogen.sh'?
If you simply downloaded the Subversion source tarball (as implied by
"1.0.4"), then you should just run ./configure, without running
autogen.sh first. This is the standard free software procedure, and
it is what our installation documentation says to do, I believe.
> Next, I ran ./configure, which terminated early with an error message.
> The output is in run_configure.log.
Did you pass any arguments to configure? Can you reattach the output
as plaintext? I was unable to unzip your attachment, unfortunately,
I'm not sure why:
$ unzip subv_logs.zip
ELF binary type "0" not known.
Abort trap
$ file subv_logs.zip
subv_logs.zip: Zip archive data, at least v2.0 to extract
$ zip
Copyright (C) 1990-1999 Info-ZIP
Type 'zip "-L"' for software license.
Zip 2.3 (November 29th 1999). Usage:
[...]
$
Strange :-(.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 23 18:19:33 2004