Changes between Initial Version and Version 1 of Ticket #63816, comment 2


Ignore:
Timestamp:
Nov 7, 2021, 5:21:07 PM (3 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #63816, comment 2

    initial v1  
    33We 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.
    44
    5 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:
     5This 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-en subports 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:
    66{{{
    77./make-hunspell-dict -j1 -all