From: Maxime Devos <maximedevos@telenet.be>
To: 52898@debbugs.gnu.org
Subject: bug#52898: cmake-build-system keeps reference to native glibc in /etc/ld.so.cache
Date: Thu, 30 Dec 2021 14:56:38 +0000 [thread overview]
Message-ID: <a92360cc648b7bb44cd8ee30b019c8587ebe160e.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
Hi,
cmake-build-system keeps a reference to the native glibc in
OUTPUT/etc/ld.so.cache, even when cross-compiling. Setting
#:make-dynamic-linker-cache? #false like in gnu-cross-build
would probably fix things. Other build systems might be
affected as well.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2021-12-30 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 14:56 Maxime Devos [this message]
2022-01-12 12:15 ` bug#52898: cmake-build-system keeps reference to native glibc in /etc/ld.so.cache Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a92360cc648b7bb44cd8ee30b019c8587ebe160e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52898@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).