[MacPorts] #72536: [linux] registry.so ends up with a fully specified *build.dir* path for the sqlite3 dependency

[MacPorts]

#72536: [linux] registry.so ends up with a fully specified *build.dir* path for the
sqlite3 dependency
--------------------+--------------------
 Reporter:  RJVB    |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  base    |    Version:
 Keywords:          |       Port:
--------------------+--------------------
 There's a weird issue on Linux (and possibly other *nices) with the build
 system of the registry Tcl extension library.

 The registry.so library ends up with a full/absolute path to
 libsqlite3.?.so ; worse, this path points into the build directory,
 crippling the installation when that directory is removed or cleaned.

 I have in fact never seen that, didn't even know it was possible and for
 now have only been able to come up with a post-destroot correction rather
 than a proper fix:
 https://github.com/RJVB/macstrop/commit/a938a6db27a2099f5562b78714cff9a1b0a7c22b
 .

 FWIW, this is not new, I simply never noticed that all my test installs
 from 2.10.0 onwards have had this problem that I simply never noticed
 because I kept the build dir. The exact path has just changed recently,
 making it easier to obtain the correct path from the stored path.
 The issue did not yet exist in 2.7.1 which still used the host's sqlite3
 library.

-- 
Ticket URL: <https://trac.macports.org/ticket/72536>
MacPorts <https://www.macports.org/>
Ports system for macOS