I am attempting to update openssl to 1.1.1 on centos 7 in order to start building OpenLDAP.
After pulling the openssl installation package and unzipping it in /usr/local/src/ I ran ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib. This command successfully configured openssl.
I then ran the make command to build openssl and got the following error:
cc1: fatal error: apps/app_rand.d: no such file or directory
compilation terminated
make(1): *** (apps/app.rand.o) Error 1
make(1): Leaving directory '/usr/local/src/openssl-1.1.1d'
make: *** (all) Error 2
The apps directory was created and does exist, but the app_rand.d file is not present inside of the apps directory.
I have downloaded all dependencies (i believe)
I am decent in linux, I have my rhcsa, but am not familiar with manually building software libraries like openssl. I have tried to do some research online but have not come up with any solutions. Any advice would be very much appreciated!
Ever since June 2020, I have been unable to update my packages with pacman -Syu. When I try, I get the following error:
(It gets up to "Checking package integrity", then shows errors like this for every single package)
error: gcc-libs: signature from "David Macek <david.macek.0#gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/gcc-libs-10.2.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
Now, helpfully, MSYS2 does have a post explaining why this occurred and how to fix it: https://www.msys2.org/news/#2020-06-29-new-packagers
However, despite following all of those steps, nothing changed and I get the same errors.
For clarity, I did the following:
curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig
pacman-key --verify msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig
pacman -U msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
Those "worked" (no errors) but didn't fix anything, so I tried:
rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate msys2
But that didn't accomplish anything either.
What do I do?
The original key updating procedure News-MSYS2 can be made to work by adding one more command:
$ pacman-key --keyserver keyserver.ubuntu.com --refresh-keys
The packager's key as delivered in msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz has expired, and needs to be refreshed.
pub rsa4096 2018-01-14 [SC] [expired: 2021-06-19]
87771331B3F1FF5263856A6D974C8BE49078F532
uid [ expired] David Macek <david.macek.0#gmail.com>
Unfortunately, the keyserver used by older version of pacman-key command is not valid anymore.
$ pacman-key --refresh-keys
gpg: error retrieving 'alexey.pawlow#gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: No name
==> ERROR: Could not update key: F40D263ECA25678A
Keyserver value in newer pacman-key was changed to keyserver.ubuntu.com by this msys2/MSYS2-keyring commit. Hence, the explicit --keyserver option for the pacman-key command at the beginning of this answer.
This worked for me. From "Nulano":
pacman -S msys2-keyring
Then use pacman -Syu as normal.
Tried the solutions at Msys 2020-06-29 - new packagers. Didn't work for me.
After trying a few other things (like disabling sourceforge mirrors) I found none worked.
Instead, I downloaded the latest tar of the project (since I cannot run the .exe) which is located at:
http://repo.msys2.org/distrib/msys2-x86_64-latest.tar.xz
Once downloaded, I went into C:/msys64/ and made a copy of the /home folder, then deleted all of the contents.
I then copied in the latest from the tar into there, and finally copied the /home folder back.
Now, MSYS2 finally works properly again. Though it does mean installing all packages over again.
I have scripts that build large numbers of debian packages. When I try to set the changelog from UNRELEASED to a specific release so that I can sign the results, I get this error on
every second dpkg-buildpackage:
gpg: signing failed: Broken pipe
gpg: dpkg-sign.fwxloLTb/libshipscomms_4.00-1.dsc: clear-sign failed: Broken pipe
dpkg-buildpackage: error: failed to sign .dsc file
Building the same package a second time immediately after this works fine.
I tried to run an incompletely installed program and then received this error. Is there anyway to solve this without the official installer? As far as I understand it, it's missing some registry entries. Can I fix this using information from the error log below?
The error log :
https://pastebin.com/VL5ps2hw
Thanks
When I try to run the software, I get this error as well:
Error Number:5. Error Source: mscorlib. This is error in paint 1.
I'm following the instruction here http://www.teratotech.com/blog/xcode-7-steps-to-easily-switch-between-multiple-environments/ to generate different schemes for different environments..
I created a testing configuration and created a new scheme to use that configuration. However, when I build and run, I'm getting this error:
<unknown>:0: error: generate-pch command failed with exit code 1 (use -v to see invocation)
error: 'AFNetworking/AFNetworking.h' file not found
#import <AFNetworking/AFNetworking.h>
1 error generated.
<unknown>:0: error: failed to emit precompiled header '/var/folders/f2/6j4b4kz54xy1vf_2gdlnrllc0000gn/T/My-Project-Header-47bffb.pch' for bridging header '/Users/me/Dev/my-project/My-Project-Header.h'
When I build with my original scheme, everything's fine... I only have 1 target. Am I missing anything?
EDIT: I'm using Cocoapods to manage my dependencies, if that makes any difference.
i solved this issue by running below commands
$ pod repo update
$ pod install
Usually such issue happens when project directory is changed or copied form some other machine.