Hi Cameron! On 9/28/21 10:59, Cameron MacPherson wrote: > i ran apt install --reinstall libffi8, restarted the system and the > following messages reappeared > > [ 16.874069] fail2ban-server[384]: illegal instruction (4) at > 3fff7ef95970 nip 3fff7ef95970 lr 3fff7ef94f90 code 1 in > libffi.so.8.1.0[3fff7ef8d000+c000] > [ 16.874154] fail2ban-server[384]: code: b1090008 f9490000 4e800020 > 00000000 00000000 00000000 60000000 60420000 > [ 16.874176] fail2ban-server[384]: code: 81230000 712a0008 41820018 > 39230004 <7c004eee> 39230020 7c004fae 4bfffaf4 > > after rm -rf ~/libffi, git clone, autogen, this time i ran ./configure with > --disable-exec-static-tramp and then copied the new libffi.so.8 to > /usr/lib/powerpc64-linux-gnu/ once again restarted the system and no more > messages on the console or in the logs about libfffi
OK, this sounds like a good verification. Thanks for testing this for me. Can you make another check and try the v3.4.2 upstream tag? $ make clean $ git clean -df $ git checkout v3.4.2 $ ./autogen.sh && ./configure && make and try again? Maybe the issue was fixed between v3.4.2 and HEAD. > september 28th is the one i just compiled replacing the one contained in > the libff8 package. i dont know the standard way of verifying which > library is being used. You can verify the library being using with the `ldd` command. For example: $ ldd `which python2.7` So, my next guess is that there is something wrong with the Debian source package. Maybe it's actually not version 3.4.2 that is being used. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
