libgcrypt | GNU crypto library

I managed to figure it out.

This is because the gpg in git for windows uses MINGW64 for the environment. And because I manually set the GNUPGHOME environment variable to a Windows path: C:/users/me/.gnupg, it will not work.

(I never use the included MINGW64 git bash, I only use cmd and add those exe, like git, gpg into PATH)

So, if you have manually set the GNUPGHOME env variable, you need to change to a MINGW64 path.

So in my case, C:/users/me/.gnupg -> /c/users/me/.gnupg

I am not sure about --homedir though.

ok, looks like i found my solution here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12406

quote from Lyle Franklin:

I hit this error when trying to build a cross-platform ARM64 docker image from a AMD64 host. However, running docker run --rm --privileged linuxkit/binfmt:v0.8 or update-binfmts --enable prior to running the build seems to avoid the issue. My understanding Docker will try to use upstream QEMU if it is installed and registered with the kernel, otherwise Docker will fallback to using a built-in forked version of QEMU. The build error above only showed up for me with the forked QEMU.

So I will probably add docker run --rm --privileged linuxkit/binfmt:v0.8 && update-binfmts --enable to my pipeline file if I encounter the error again, for now running it once solved the issue.

If I get the ldd-output right the Library libusb is missing:

Mem was not quite enough for me to compile. Problem solved.

There is only 1g1c on my VPS, and I'm running an Nginx and sidekiq. The mem is only about 600m in usual cases. Simply mem wasn't quite enough to compile and build.

you should update flutter (Channel stable) version to 2.0.3 . This version of flutter run don't have this issue.

the universal solution for this problem is to uninstall flutter that you've installed from snap and install it from AUR.

installing flutter from AUR-->yay -S flutter

you might encounter some permission problem. here's how to fix permission:

Create a new group flutterusers, add the default user to the group, then change permissions on the folder /opt/flutter.

Your dask and distributed versions have gone out of sync, 2021.4.0 versus 2021.4.1. Updating dask should fix this. Note that you need to ensure that the exact same versions are also in the environment you are using for YARN.

Since you've installed this using brew you are trying to link against libraries built for the Mac. You need to build those libraries for iOS. Note this will typically involve making a fat binary of the different architectures you'll need per library. You can easily test this for fftw and see if the linker errors disappear. Here are some references to build or download a pre-built version.

https://github.com/godock/fftw-build

In theory once you link up against the iOS version, you should see errors like

In my personal setup I have added the signingkey to the user section.

This is normal behavior in CMake. When compiling you binaries the rpath to the dependencies is set in the binary, but stripped when installing it.

By default if you don't change any RPATH related settings, CMake will link the executables and shared libraries with full RPATH to all used libraries in the build tree. When installing, it will clear the RPATH of these targets so they are installed with an empty RPATH. Source

When looking up runtime dependencies the rpath is preferred over the default directories (see https://stackoverflow.com/a/33520976/4181011). But since the rpath was removed from your library it doesn't know about you "out-of-default-directories"-dependencies.

You can manipulate the lookup with LD_LIBRARY_PATH, LD_PRELOAD or by adding the additional path to the lookup directories using ldconfig.