[MacPorts] #63816: hunspell-en* @2020.12.07: usage: ./make-hunspell-dict -all | -one <dict-name> <parms file> (was: hunspell-en* @ 2020.12.07 dictionary install errors)

[MacPorts]

#63816: hunspell-en* @2020.12.07: usage: ./make-hunspell-dict -all | -one <dict-
name> <parms file>
-------------------------------------------------+-------------------------
  Reporter:  rsrock                              |      Owner:  (none)
      Type:  defect                              |     Status:  new
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.7.1
Resolution:                                      |   Keywords:
      Port:  hunspell-en_US hunspell_en_GB_ise   |
  hunspell_en_US_large                           |
-------------------------------------------------+-------------------------
Changes (by ryandesign):

 * cc: cjones051073 (added)
 * version:   => 2.7.1


Comment:

 Ok, I see the problem on my machine too with High Sierra. Not OS version
 dependent.

 We have successful builds of this port on all OS versions back when the
 port was updated to this version in 2020, but it fails to build now.

 This is because of [changeset:d148e62c89c0fee07e202dd64b132e6134e7537e
 /macports-base a change in MacPorts base] that occurred after that.
 MacPorts now adds the flag `-j1` for any build systems that it believes to
 be `make`-compatible, whereas before it would only add a `-j` flag when
 the value was greater than one. The problem is that the hunspell ports
 build using the command `./make-hunspell-dict` which MacPorts perceives as
 being `make`-compatible, though it is not. This results in the actual
 build command being, erroneously:
 {{{
 ./make-hunspell-dict -j1 -all
 }}}
 and the response being:
 {{{
 usage: ./make-hunspell-dict -all | -one <dict-name> <parms file>
 }}}
 rather than an actual build occurring. That is why the file it is trying
 to install it not there.

 We need to tell the port to suppress the addition of the `-j1` flag, if I
 can remember how to do that.

 This fallout from that MacPorts base change is yet more evidence, in
 addition the several times it's come up previously, of why the change
 should perhaps have been restricted to only ninja, since that is the only
 build system that needed the change.

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