From: Paul Naidoo <paul.naidoo@lynkeos.co.uk>
To: binutils@sourceware.org
Subject: `strip: X.so could not create temporary file to hold stripped copy: cause of error unknown`
Date: Tue, 21 Feb 2023 20:43:56 +0000 [thread overview]
Message-ID: <d7edf6b4-66f2-f920-c811-06dfaacd2eb1@lynkeos.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
Hi there,
I am trying to run a singularity container on a CentOS7 host, which
contains an application with Qt5 dependencies.
I am experiencing an error where |libQt5Core.so.5| can not be used
because of an incompatibility with the linux kernel version for CentOS7:
|uname -r 3.10.0-1160.76.1.el7.x86_64 |
The error given is: |
error while loading shared libraries: libQt5Core.so.5: cannot open
shared object file: No such file or directory|.
Searching online, various posts (e.g.
<https://askubuntu.com/a/1163268/1041180>) conclude the solution is to
execute the following command in order to impose compatibility with
older kernels:
|strip --remove-section=.note.ABI-tag
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5|
However executing the command returns the error: |strip:
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: could not create temporary
file to hold stripped copy: cause of error unknown|
I have confirmed:
* the container works on systems with a newer kernel
* I am running the container with the |--writable| flag, and as |sudo|
* I have the correct path:
o
|whereis libQt5Core.so.5||
libQt5Core.so.5: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5|
I am at a dead end as to why the strip command is not working. I have
been unable to find a solution online. As strip is a part of the
binutils suite, I was hoping that someone might be able to point me
towards a solution, or at least a line of investigation?
Sincerest thanks in advance!
Cheers,
Paul
next reply other threads:[~2023-02-21 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:43 Paul Naidoo [this message]
2023-02-22 0:02 ` Alan Modra
2023-02-22 0:24 ` Andreas Schwab
2023-02-22 1:35 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7edf6b4-66f2-f920-c811-06dfaacd2eb1@lynkeos.co.uk \
--to=paul.naidoo@lynkeos.co.uk \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).