[MacPorts] #72090: gstreamer1-gst-plugins-bad @1.24.9: error: no member named 'logical_processors' in 'struct EbSvtAv1EncConfiguration'

[MacPorts]

#72090: gstreamer1-gst-plugins-bad @1.24.9: error: no member named
'logical_processors' in 'struct EbSvtAv1EncConfiguration'
-----------------------------------------+--------------------
  Reporter:  amadeus24                   |      Owner:  (none)
      Type:  defect                      |     Status:  new
  Priority:  Normal                      |  Milestone:
 Component:  ports                       |    Version:  2.10.5
Resolution:                              |   Keywords:
      Port:  gstreamer1-gst-plugins-bad  |
-----------------------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:8 amadeus24]:
 > BTW, I experience more & more crashes ({{{conftest}}} & {{{bsdtar}}})
 during ports installation.\\

 According to your bsdtar crash log, the problem is:

 {{{
 Library not loaded: /opt/local/lib/libiconv.2.dylib
 Referenced from: <E15357B7-45C9-3A97-A26B-60D78BB39D80>
 /opt/local/bin/bsdtar
 Reason: tried: '/opt/local/lib/libiconv.2.dylib' (no such file),
 '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libiconv.2.dylib' (no
 such file), '/opt/local/lib/libiconv.2.dylib' (no such file)
 }}}

 That's weird since bsdtar is provided by the libarchive port which
 declares a dependency on the libiconv port so the libiconv library should
 be there.

 It's also weird that MacPorts bsdtar is being used at all; the tar program
 that comes with macOS should be used instead.

 -----

 Your conftest log says it crashed because:

 {{{
 %%n used in a non-immutable format string: %s
 }}}

 conftest is the name of a program created temporarily by autoconf-based
 configure scripts to test your system. A crash with this message probably
 means that particular test is using a problematic type of format string
 that Apple now considers insecure, therefore Apple causes any program
 using such a format string to crash. The solution is to fix this
 particular test in whatever port's configure phase was running when this
 crash log was generated.

 -----

 Neither of these problems seem like they're related to this bug report.
 I'll leave analysis of the ffmpeg crash report to someone else.

 -----

 Installing things in /usr/local can cause problems for MacPorts and is not
 recommended. See wiki:FAQ#usrlocal.

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