Ld-linux-aarch64.so.1(glibc_2.17)(64bit) _VERIFIED_ Download
Dulcie Yauck
I know it is not a problem with my machine, because it successfully installs another project rpm I have made previously. Some of the dependency failures are on packages which are already installed, and some of them are packages which are not found by yum. For example, I have tried to install ld-linux-aarch64.so.1()(64bit) several different ways, even running a yum search on 'ld' and 'linux' and have not found any output. I am also confused by some packages trying to aske for extra details in their perentheses. 'libstdc++.so.6(CXXABI_ARM_1.3.3)' seems to be asking for libstdc++.so.6, which is part of libstdc++ but I can't find any details on CXXABI_ARM_1.3.3, or what it means, or why it wants it, or where it gets the request for it. I do know that a lot of these dependencies are part of the 'Development Tools' group, which I have already installed, both individually, and through yum groupinstall. 'libatk-bridge-2.0.so.0()(64bit)' does not seem to exist either. I have tried using rpm-builder from npm and straight up making a .spec file and running rpm-build. here is the Specfile I have made:
The files you mentioned in particular (ld-linux-aarch64.so.1()(64bit) and libstdc++.so.6(CXXABI_ARM_1.3.3)) are ARM and not x86_64. I'm assuming you've bundled up something else, so the RPM dependency generator is finding these .so files and assuming you need them to deploy. More likely, they're a payload that you are serving up or something, so don't need to be executable.