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

Re: [PATCH] Fix --enable-dso for Darwin/Mac OS X

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-02-15 18:23:14 CET

On Mon, 2005-02-14 at 20:23, Eric Gillespie wrote:
> > I don't like how this change affects the existing platforms. We rely on
> > LD_LIBRARY_PATH for the dynamically linked libraries; why shouldn't we
> > be relying on it for the dynamically loaded ones? If someone relocates
> > a Subversion binary install, they can no longer use front-end scripts
> > and LD_LIBRARY_PATH to make it work, with this change.

> When you have the source, why do you need to relocate binaries?

No working compiler? Insufficient knowledge? Relocating a binary
package is not generally a good idea, but that's not an excuse for us to
use the wrong behavior for dynamically loaded libraries.

> But, if we allow relocation today and want to continue providing
> it, can we do this just for Darwin?

I don't know enough about Darwin to judge whether this is a good idea.
If it's necessary or standard practice on that platform, then sure.

> > (And I expect it's how you broke the test suite; you forced the program
> > to load the installed libraries, rather than the built ones.)
> Then why am i able to run svnadmin and svn from the working copy?
> Is the test suite bypassing the magic libtool scripts?

I don't know why you are able to run svnadmin and svn from the working
copy. I don't see how the magic libtool scripts can fix this problem;
they can relink the executable, but they can't change the value of

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 15 18:46:51 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.