pspp @1.4.1, pspp-devel @1.5.3_1: undefined symbols

[ryandesign (Ryan Carsten Schmidt)]

pspp-devel @1.5.3_1 doesn't build on macOS Big Sur due to undefined symbols:

​https://build.macports.org/builders/ports-11_x86_64-builder/builds/26086/steps/install-port/logs/stdio

Undefined symbols for architecture x86_64:
  "_F_8_0", referenced from:
      _cmd_mrsets in liblanguage.a(mrsets.o)
      _decode_spvdx_table in liboutput.a(liboutput_la-spv-legacy-decoder.o)
  "_add_permanent_ordering_transformation", referenced from:
      _cmd_rank in liblanguage.a(rank.o)
  "_add_transformation", referenced from:
      _cmd_compute in liblanguage.a(compute.o)
      _cmd_if in liblanguage.a(compute.o)
      _cmd_count in liblanguage.a(count.o)
      _cmd_debug_xform_fail in liblanguage.a(fail.o)
      _cmd_sample in liblanguage.a(sample.o)
      _cmd_recode in liblanguage.a(recode.o)
      _cmd_select_if in liblanguage.a(select-if.o)
      ...

...and tons more.

I see libtool being used for this build so this is likely the well-known libtool defect on macOS 11 and later that needs to be patched by copying or adapting the relevant portions of the patchfile in the libtool port.

Curiously we do have a successful build on big sur of exactly one version of pspp-devel: @1.5.2_3. Not sure why that version was special and different from both earlier & later versions.

pspp probably needs the same fix.

[nerdling (Jeremy Lavergne)]

In e5fae74c167c45790f3fcf9164e6d9b4945ac021/macports-ports (master):

pspp-devel: upgrade to g797d4c

• use python3.10
• fix #62659