From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 60584-done@debbugs.gnu.org,
"Sébastien Rey-Coyrehourcq"
<sebastien.rey-coyrehourcq@univ-rouen.fr>,
"Greg Hogan" <code@greghogan.com>,
60875-done@debbugs.gnu.org
Subject: bug#60875: Grafting breaks with clang-toolchain@13
Date: Tue, 17 Jan 2023 16:13:45 +0100 [thread overview]
Message-ID: <873589gpna.fsf@gnu.org> (raw)
In-Reply-To: <Y8aRnPltaRibXWT7@jasmine.lan> (Leo Famulari's message of "Tue, 17 Jan 2023 07:16:28 -0500")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Jan 17, 2023 at 11:23:42AM +0100, Ludovic Courtès wrote:
>> The file exists but it’s a dangling symlink:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ ls -l /gnu/store/12wnswvdc1mk9cr498dxflxim4qm2pyq-clang-toolchain-13.0.1/lib/libz.so.1.2.11
>> lrwxrwxrwx 1 guixbuilder01 guixbuild 74 Jan 17 10:36 /gnu/store/12wnswvdc1mk9cr498dxflxim4qm2pyq-clang-toolchain-13.0.1/lib/libz.so.1.2.11 -> /gnu/store/v8d7j5i02nfz951x1szbl9xrd873vc3l-zlib-1.2.12/lib/libz.so.1.2.11
>> $ stat -L /gnu/store/12wnswvdc1mk9cr498dxflxim4qm2pyq-clang-toolchain-13.0.1/lib/libz.so.1.2.11
>> stat: cannot statx '/gnu/store/12wnswvdc1mk9cr498dxflxim4qm2pyq-clang-toolchain-13.0.1/lib/libz.so.1.2.11': No such file or directory
>> --8<---------------cut here---------------end--------------->8---
>
> Merged with <https://issues.guix.gnu.org/issue/60584>
Fixed in c4a8762e529dc3f8af89dde5dbcbb82f2a4088a3.
Now it would be good to see why ‘clang-toolchain’ has this dangling
symlink.
Thanks,
Ludo’.
prev parent reply other threads:[~2023-01-17 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 10:23 bug#60875: Grafting breaks with clang-toolchain@13 Ludovic Courtès
2023-01-17 12:16 ` Leo Famulari
2023-01-17 15:13 ` Ludovic Courtès [this message]
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=873589gpna.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60584-done@debbugs.gnu.org \
--cc=60875-done@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=leo@famulari.name \
--cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
/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).