[MacPorts] #68470: Upgrade to 0.080 incompatible with clang (aes feature not enabled)

[MacPorts]

#68470: Upgrade to 0.080 incompatible with clang (aes feature not enabled)
------------------------+--------------------------
 Reporter:  pcafstockf  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  High        |  Milestone:
Component:  ports       |    Version:  2.8.1
 Keywords:              |       Port:  p5.34-cryptx
------------------------+--------------------------
 Rolled back to 0.078, so no longer have the logs on my machine, but the
 (buildbot for
 HighSierra)[https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/206727/steps
 /install-port/logs/stdio] shows the same problem in in the stdio log.

 {{{
 /usr/bin/clang -Iltm -Iltc/headers -DLTC_SOURCE -DLTC_NO_TEST
 -DLTC_NO_PROTOTYPES -DLTM_DESC -fno-common -DPERL_DARWIN  -pipe -Os  -fno-
 strict-aliasing -fstack-protector-strong -I/opt/local/include
 -DPERL_USE_SAFE_PUTENV   -O3  -pipe -Os -arch x86_64  -I/opt/local/include
 -DARGTYPE=4 -c ltc/ciphers/blowfish.c -o ltc/ciphers/blowfish.o
 ltc/ciphers/aes/aesni.c:79:26: error: '__builtin_ia32_aeskeygenassist128'
 needs target feature aes
          rk[4] = rk[0] ^ setup_mix(temp, 3) ^ rcon[i];

 }}}
 Just for giggles, I also overrode the compiler whitelist/fallback to force
 macports-clang (currently set to clang-16), but not surprisingly, same end
 result (since the --maes flag is not passed).

 I also changed into the src directory and manually compiled that file,
 **adding the -maes flag**, and that particular file compiled just fine.

 My workaround was just to rollback to the 0.078 version.

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