#59712 closed defect (wontfix)
subversion @1.13.0 runs svnversion during the build, which fails
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | danielluke (Daniel J. Luke) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | Cc: | ||
Port: | subversion |
Description
subversion evidently runs the just-built svnversion at some point during the build. 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 they were built. (I assume that the fix will be setting that variable.)
This does not cause the build of subversion to fail, but whatever it's running svnversion for can't be getting the correct result. Whether that's important, I don't know.
On old Mac OS X versions like 10.6 that ship with an old copy of subversion, the failure is:
Symbol not found: _svn_pool_create_allocator Referenced from: /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_devel_subversion/subversion/work/subversion-1.13.0/subversion/svnversion/svnversion Expected in: /usr/lib/libsvn_subr-1.0.dylib
On new macOS versions like 10.14 that don't ship with subversion, the failure is:
Library not loaded: /opt/local/lib/libsvn_wc-1.0.dylib Referenced from: /opt/local/var/macports/*/svnversion Reason: image not found
Attached are two crash logs I found on our buildbot workers.
Attachments (2)
Change History (6)
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | svnversion_2019-11-03-203117_localhost.crash added |
---|
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | svnversion_2019-10-30-183322_mojave.crash added |
---|
comment:1 Changed 5 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 5 years ago by danielluke (Daniel J. Luke)
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
comment:3 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Ok. I've reported it to the developers here: https://svn.haxx.se/users/archive-2019-11/0007.shtml
That's almost certainly from the revision-install target in the top level makefile. If it ran, it would populate ${prefix}/include/subversion-1/svn-revision.txt with "Unversioned directory", since it crashes that file gets populated with "unknown". I don't think it actually matters.