Not sure if anyone is still using this, but I did update OpenSSL 1.0.2 to fix the latest three CVEs: CVE-2021-23839 CVE-2021-23840 CVE-2021-23841 All branches updated. Additionally master has been upd

Change is fine. I'm not having the time to merge and test build right now. Paul E suggested someone else might be able to, that is fine with me. --Mark

Looking at the config.log, I only see the standard Yocto Project (nativesdk) paths, as well as: --disable-asm --without-capabilities I'm building on 18.04.4 LTS, I think it's a fairly standard config,

Note, this is still happening. Using meta-mingw w/ gatesgarth to build, and including libgcrypt I get the same failure. The failure resolves with "--disable-amd64-as-feature-detection". Looking at the

A quick review of this looks fine. I'm currently swamped with some work stuff and ELC-E this week. I intend to get to this (and a few other contributions next week. If you don't see anything from me n

It's not up to OE/YP to verify alternatives, it's up to the people providing the alternatives. The question is, is this a MESA dependency or a virtual/gl dependency. If it's the former, then mesa is c

This could be an issue with your host if the host is too old. Unfortunately I've not worked with the releases that are that old. However, Xilinx did just release their 'Zeus' based rel-v2020.1 version

This is what I would suggest. Have the recipe itself set the fallback URI as the main URL. SRC_URI = "git://example.com/my/repository/uri;proto=https" PREMIRRORS_prepend = "git://example.com/my/reposi

Yes, it doesn't do anything if the generated toolchain isn't mingw.. and AFAIK, we're only build cross-canadian there. (binutils and others don't appear to have this option, unless I just missed it.)

Ya, it backports to Zeus fine. That is as far back as I've looked. --Mark

In gcc 8, the behavior of GCC changed and expansion of wild cards to calls of gcc were disabled by default. This behavior may be required by some (poorly written) makefiles. This will allow someone to

I'll reply with a private email to where you can get a copy of the build directory. I tried this and it didn't appear to make a difference. I only see the problem when building for mingw32. I've never

amd64 optimization when using with mingw32 sometimes results in: | ../../libgcrypt-1.8.4/cipher/rijndael-tables.h:103:24: error: expected ']' before '.' token | 103 | #define encT enc_tables.T and the

amd64 optimization when using with mingw32 sometimes results in: | ../../libgcrypt-1.8.4/cipher/rijndael-tables.h:103:24: error: expected ']' before '.' token | 103 | #define encT enc_tables.T and the

He is correct, this is shared between all package users. But with that said, there is a base filesystem package and an associated 'syncing' file for all other users. The is a recipe called 'base-files

As of GCC 8, plugin support is available with mingw. If the plugins are enabled in the regular binutils/gcc configurations, carry over that configuration with the mingw versions as well. When plugins

Thanks for the pull request.. pushed. --Mark

I tried to apply this patch, but unfortunately it's corrupt. Likely by an exchange server or outlook. If you can, you can generate a pull request at: https://github.com/mhatle/meta-openssl102-fips I p

Sorry, I missed this when it was originally sent. I've updated master with these patches. Thanks! Please check master, if you see anything missing please let me know. --Mark

Should this be applied only to the warrior branch? I don't typically build warrior branch, but I'm happy to accept patches if you can verify it's working properly. --Mark