Re: Proposed update to bmake-20240711

[Jonathan Perkin <jperkin%mnx.io@localhost>]

* On 2024-07-12 at 17:47 BST, Simon Gerraty wrote:

> You can use --with-defshell=sh=/path/to/mksh if you want to force it to
> use the sh specification - which may or may not provide better results
> (though I would not be too hopeful).

Well, it's different:

  ===> Testing for bmake-20240711
  cd /work/git/pkgsrc/devel/bmake/work/bmake/unit-tests && MAKEFLAGS= /work/git/pkgsrc/devel/bmake/work/bmake/bmake -r -m / test
  bmake[2]: "/work/git/pkgsrc/devel/bmake/work/bmake/unit-tests/Makefile" line 47: warning: "mkdir -p /var/folders/w7/88jp9ds51v7f5pl61gzkhmt40000gn/T//uid501" exited on a signal
  bmake[2]: "/work/git/pkgsrc/devel/bmake/work/bmake/unit-tests/Makefile" line 512: warning: Skipping broken tests: sh-flags shell-ksh
  *** Signal 11

In true macOS fashion I don't know what is generating this, I've added 
codesign signatures to both bmake and mksh but neither is generating a 
coredump.

I wouldn't worry too much, we only have to use mksh in pkgsrc because 
using a system shell breaks System Integrity Protection, so this is very 
much a corner case.  It's clear that bmake is functioning ok though.

--
Jonathan Perkin   -   mnx.io   -   pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com