[MacPorts] #60165: meson @0.53.2 produces on PPC Mac OS X 10.4.11, Tiger, faulty files with illegal loader switch '-Wl, -rpath, @loader_path/'

[MacPorts]

#60165: meson @0.53.2 produces on PPC Mac OS X 10.4.11, Tiger, faulty files with
illegal loader switch '-Wl,-rpath, at loader_path/'
------------------------+-----------------------
  Reporter:  ballapete  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.2
Resolution:             |   Keywords:  tiger ppc
      Port:  meson      |
------------------------+-----------------------

Comment (by ballapete):

 Replying to [comment:4 kencu]:
 >
 > Installing the libraries in the build directory with the full pathname
 to the library might work.

 This works at least for the optional step `meson test`. I have not yet
 tried `port upgrade <whatever>`.

 > We can find the path to the build directory with
 {{{env.get_build_dir()}}} so we can get that far without too much trouble.
 And we can modify {{{get_soname_args}}} to return the install name as that
 pathname + '/' + prefix + shlib_name.
 >
 > The part I'm missing is the bit of the path between the base build_dir
 path and the actual library target path relative to the build_dir.

 I presume both statements express that you would get a path name of
 `/opt/local/var/macports/build/_opt_local_var_..._<whatever>/work/build/lib<whatever>-1.0.0.dylib`
 instead of the correct value
 `/opt/local/var/macports/build/_opt_local_var_..._<whatever>/work/build/*<whatever>*/lib<whatever>-1.0.0.dylib`
 (at least in case of `<whatever> = atk` which I am testing). Some `port or
 project name` is missing between `.../build/` and `/lib<whatever>...`.

-- 
Ticket URL: <https://trac.macports.org/ticket/60165#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS