On 17.11.2019 22:24, Nathan Hartman wrote: > On Sun, Nov 17, 2019 at 2:47 PM Ryan Schmidt <subversion- > 2...@ryandesign.com <mailto:2...@ryandesign.com>> wrote: > > Hi, I noticed this bug in subversion on macOS. I reported it here: > > > > https://trac.macports.org/ticket/59712 > > > > But it's really an upstream issue so I would like to report it here > > as well. > > > > The subversion build evidently runs the just-built svnversion at > > some point. This crashes, because the libraries it's linked with > > haven't been installed yet, and I guess it's not setting > > DYLD_LIBRARY_PATH to the path where the built libraries are. I > > assume that the fix will be setting that variable. > > I am not an expert on this subject but IIRC setting DYLD_LIBRARY_PATH > will *not* help because of something called SIP (System Integrity > Protection) on macOS.
SIP only affects how DYLD_LIBRARY_PATH works for system binaries, not stuff you build yourself. For example, our test suite runs just fine in the build directory with DYLD_LIBRARY_PATH set, but the Python (2) bindings test suite does not, because it's run by the system Python binary. Anyway: the short-term solution would be to run 'make install' with '-j1' so that local-install runs before revision-install. The long-term solution is to either remove that useless stanza from the Makefile, or add proper dependencies between those two targets. -- Brane