Steve Cohen <scohen@javactivity.org> wrote on 02/06/2005 11:55:29 AM:
> Mark Phippard wrote:
>
> >
> > Are you going to try to build javahl? Let us know how that goes, you
will
> > definitely see a performance boost.
> >
>
> Not well. I had installed subversion-1.1.3 from an RPM on my redhat
> system. I tried to build the source rpm as a way of getting the source
> and that fails. After about an hour of thrashing about, mostly running
> various tests, which pass, I run into this:
[snip]
>
> RPM build errors:
> user dsummers does not exist - using root
> group dsummers does not exist - using root
> user dsummers does not exist - using root
> group dsummers does not exist - using root
> user dsummers does not exist - using root
> group dsummers does not exist - using root
> Bad exit status from /var/tmp/rpm-tmp.37183 (%build)
>
> and the build of the binary RPM from source aborts.
>
> Gaah. I lack the patience for this. What are these tests actually
> testing (since all we're doing here is building an RPM, which
> presumably, hasn't been installed yet)? What if anything can I do to
> resolve the errors? And why, if these tests are failing, was I able to
> install the downloaded BINARY RPM for the same version of subversion,
> which, as far as I am able to tell, simply works?
>
> I am starting to feel that subversion - and subeclipse - are far too
> tied up with the internal of my system for my tastes.
Subversion just has a bunch of unit tests that you can run as part of the
make. I am not sure why they would fail, but there could be a legitimate
reason. You could potentially just ignore them as it is possible the
problems were just in the test environment itself.
On Linux, you are right that Subversion is very tied up with the internals
of your system. This is because it uses so many common components like
APR, BDB and OpenSSL. Worse, it tends to need recent versions of all of
them. Since so much other Linux software uses these same components it
can lead to issues. It is all over my head.
Subclipse is just caught in the middle of all of this. We are just a
normal Eclipse java plugin, but since we have to use JavaHL, which is part
of Subversion, we cannot avoid being dragged into these issues as well.
I would suggest that you try to follow the normal build instructions that
were posted previously.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon Feb 7 06:13:27 2005