[MacPorts] #67975: john @1.9.0_1: does not install executable (maybe arm64-related)

[MacPorts]

#67975: john @1.9.0_1: does not install executable (maybe arm64-related)
--------------------+--------------------
 Reporter:  JDLH    |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  ports   |    Version:  2.8.1
 Keywords:          |       Port:  john
--------------------+--------------------
 Port john @1.9.0_1 appears to install no executable. This may be limited
 to arm64 (M1, Apple Silicon) architectures.

 **How to reproduce**:
 Install port "john". I used a MacBook Pro with an Apple M1 Max CPU and
 macOS 12.6.8 Monterey. Then attempt to run john's executable.
 {{{
 % sudo port -k install john
 --->  Fetching archive for john
 --->  Attempting to fetch john-1.9.0_1.darwin_21.arm64.tbz2 from
 https://packages.macports.org/john
 --->  Attempting to fetch john-1.9.0_1.darwin_21.arm64.tbz2.rmd160 from
 https://packages.macports.org/john
 --->  Installing john @1.9.0_1
 --->  Activating john @1.9.0_1
 --->  Updating database of binaries
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 --->  No broken ports found.
 --->  Some of the ports you installed have notes:
   john has the following notes:
     You'll find the john files under /opt/local/share/john/
 % john
 zsh: command not found: john
 }}}

 **Observed behaviour**:

 {{{
 % john
 zsh: command not found: john
 % ls -l /opt/local/bin/john
 lrwxr-xr-x  1 root  admin  26  7 Nov  2021 /opt/local/bin/john ->
 /opt/local/share/john/john
 % ls -l /opt/local/share/john/john
 ls: /opt/local/share/john/john: No such file or directory
 }}}

 **Expected behaviour**: executable for john runs, without errors.

 **Discussion**:
 Subport "john-jumbo" also does not install an executable, but this is
 because it has a build failure. See ticket #67973.

 Tickets #67973 and #62859 are related to building ports "john" and "john-
 jumbo" on arm64 architectures. It is not clear if they are related to this
 issue.

 I suspect that this may be arm64-related, but I don't have evidence for
 that. I can't image that this has never worked, and arm64 architectures
 are the most recent change which seems relevant.

-- 
Ticket URL: <https://trac.macports.org/ticket/67975>
MacPorts <https://www.macports.org/>
Ports system for macOS