[MacPorts] #69603: gjs @1.80.1: Undefined symbols for architecture x86_64: "std::__1::__libcpp_verbose_abort(char const*, ...)"

[MacPorts]

#69603: gjs @1.80.1: Undefined symbols for architecture x86_64:
"std::__1::__libcpp_verbose_abort(char const*, ...)"
----------------------------+------------------------
  Reporter:  christophecvr  |      Owner:  dbevans
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:
Resolution:                 |   Keywords:  highsierra
      Port:  gjs            |
----------------------------+------------------------

Comment (by christophecvr):

 Replying to ryandesign: .

 Yes the bug is filed for macports . Building outside macports was only a
 try to see if I could have more info to trace the problem.
 But now I did not set a DYLD_LIBRARY_PATH in bash.profile. and not use
 export DYLD_LIBRARY_PATH=... . The used lib paths are normally set via the
 autotools and or build tools such as macports self,or configure or meson
 or cmake or ... But quit possible that meson does set sometimes the wrong
 lib at wrong time. As info my bash.profile has only one export and that is
 :

 {{{
 export MANPATH="/opt/local/share/man:$MANPATH"
 }}}

 The paths are set in /private/etc/paths  file . So the paths are by my
 then always (as user or sudo or sudo -i) the same.
 these are

 {{{
 /opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin
 }}}

 For the rest I kept all macos defaults sudo login bash is /bin/sh user
 login bash is /bin/bash.
 Just one little change in /private/etc/sudoers I added

 {{{
 Defaults        always_set_home
 }}}

 then excecuting a command with sudo like for example gedit will use
 /var/root as home dir for the caches and settings and so not make those
 settings unchangable in users home dir.

 But I just had plenty of info further here to investigate and try to find
 real cause and solution. It maybe a upgrade somewhere wich is the cause.
 Even meson has had a upgrade not so long ago perhaps this may also trigger
 some wrongly set libs due to deprecated or not used parameters who does
 not fail the configure phase.

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