p5.34-cryptx @0.80.0: error: '__builtin_ia32_aeskeygenassist128' needs target feature aes

[pcafstockf (Frank Stock)]

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.

[balanco]

this is to confirm that:

1. sudo port

2. edit p5.34-cryptx (loads the port file in your favourite editor)

3. insert the following single line (I added it after the long_description … line):

   configure.cflags-append  -maes
   

4. save the modified Portfile and exit your editor

5. install p5.34-cryptx

appears to have worked OK on my Mac OS X 10.15.7 (build 19H2026) MBP

☞ big thanks to @pcafstockf for having done all the hard work, and looking forward to a "working" release in due course...

[ryandesign (Ryan Carsten Schmidt)]

Has anybody bothered to report the problem to the developer of cryptx? They can't fix problems they don't know about.

Looking around their issue tracker, I see the same error reported in ​https://github.com/DCIT/perl-CryptX/issues/97 but that issue was closed. I see a similar error reported in ​https://github.com/DCIT/perl-CryptX/issues/100 with a possible fix having been submitted in ​https://github.com/DCIT/perl-CryptX/pull/99. Try that.