Could you please share your config.log?

For avx2 support, you have to build core with depends as there's a patch for intel-ipsec-mb. We're investigating the possibility of removing the patch for 1.14.7. You can find more information about depends at: https://github.com/dogecoin/dogecoin/tree/master/depends

Thank you @edtubbs for information. Per @patricklodder request, I'm attaching my config.log

I am also examining these logs and will check on the use of depends, as advised.

P.S. My Mac recently went kaput so I won't be able to address Mac-related issues in #3260 for a while. So I dug up my old Dell laptop instead 😎

For avx2 support, you have to build core with depends as there's a patch for intel-ipsec-mb

Based on what I see in config.log, this is likely the cause. It would be good to test for that patch with ./configure.

P.S. My Mac recently went kaput so I won't be able to address Mac-related issues in #3260 for a while.

There's still review pending on #3308 - once that is done I'll propose something for the CI part of #3260 including that patch

Hi,

Thank you again for prompt responses. The issue is fixed when applying suggested patch, which I was able to re-create for Gentoo system like so:

diff --git a/lib/include/sha_generic.h b/lib/include/sha_generic.h
index 9329da2..26d6d4e 100644
--- a/lib/include/sha_generic.h
+++ b/lib/include/sha_generic.h
@@ -323,7 +323,7 @@ void sha_generic_1block(const void *data, void *digest,
                 return;
         }
 #endif
-        sha_generic_init(digest, sha_type);
+        // sha_generic_init(digest, sha_type);
         sha_generic_one_block(data, digest, is_avx, sha_type);
 #ifdef SAFE_DATA
         clear_scratch_gps();

which, as I understand it, boils down to commenting out sha_generic_init() function.

I applied this patch to app-crypt/intel-ipsec-mb and was able to successfully launch and run Dogecoin Core with avx2 enabled.

Since intel-ipsec-mb is conveniently provided in Gentoo's Guru package overlay, I have to find a way to automatically patch app-crypt/intel-ipsec-mb from my own ebuild and I am not yet sure if it's possible, so I am not out of the woods with this issue just yet. However, since in a general sense a patch to this problem is available, I guess it may not be considered a bug in this sense then?

However, since in a general sense a patch to this problem is available, I guess it may not be considered a bug in this sense then?

To me, the "bug" is simply a missing check during configuration, where we make sure that when someone custom compiles against a non-patched intel-ipsec-mb, we error out at that time, and not at runtime.

To me, the "bug" is simply a missing check during configuration, where we make sure that when someone custom compiles against a non-patched intel-ipsec-mb, we error out at that time, and not at runtime.

Hi,

I have recently implemented this process gentoo/guru@5e67e95

Thank you,
Victor.