[MacPorts] #72151: neomutt @20240329 -doc: Error: No usable pkg-config

[MacPorts]

#72151: neomutt @20240329 -doc: Error: No usable pkg-config
------------------------+----------------------
  Reporter:  kprussing  |      Owner:  l2dy
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.10.5
Resolution:             |   Keywords:
      Port:  neomutt    |
------------------------+----------------------

Comment (by kprussing):

 **TL;DR**: I managed configure and build neomutt by building the
 distributed jmish0.c before running configure. It works as a one off, but
 I don't know how it would integrate with MacPorts.

 After a bit more digging, I found a few more details.  It appears that the
 [https://msteveb.github.io/autosetup/ autosetup tool] used by neomutt to
 configure is relying on the fact that the user has a newish version of
 `tclsh`. In particular, it appears that older versions of `tclsh`
 [https://narkive.com/HVNgTdzH.2 do not respect `TMPDIR`] and use a
 hardcoded value instead.

 Looking at the first script run by configure
 [https://github.com/neomutt/neomutt/blob/main/autosetup/autosetup-find-
 tclsh (`autosetup/autosetup-find-tclsh`)], the tool will look for the
 interpreter with a preference of a local build of
 [https://jim.tcl.tk/index.html/doc/www/www/index.html Jim Tkl]. As a test,
 I hand built the local version of jimsh0 (`cc -o jimsh0
 autosetup/jimsh0.c`). When I ran configure, it ran to completion with no
 complaints about not finding `pkg-config` or any other problems triggered
 by the permissions on `/tmp`. Then building the executable completes and
 the executable runs with no segfault.  So, a potential solution could be
 to build the local version of `jimsh0` before running configure instead of
 patching the build scripts.

 I am not familiar enough with the MacPorts architecture to make a real
 recommendation. Building the interpreter could be a pre-configure step,
 but that would only fix this port. I would not propagate to any other port
 using the autosetup tool.

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