From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 30395-done@debbugs.gnu.org, 30820-done@debbugs.gnu.org
Subject: bug#30820: Chunked store references in compiled code break grafting (again)
Date: Wed, 21 Mar 2018 21:59:39 +0100 [thread overview]
Message-ID: <87605pf8lg.fsf@gnu.org> (raw)
In-Reply-To: <87bmfic4pz.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 21 Mar 2018 07:39:20 +0100")
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
>> Good news! Commit e288572710250bcd2aa0f69ce88154d98ac69b29 adjusts
>> ‘gcc-strmov-store-file-names.patch’ in ‘core-updates’ to correctly deal
>> with this case:
> […]
>> I built everything about to ‘gcc-final’ in ‘core-updates’. I checked
>> manually that none of the /gnu/store references in libc-2.26.so were
>> chunked.
>
> Wow, thank you so much for fixing this!
It turned out to be easier than the first time. ;-)
> Is this an option that we can suggest to the GCC developers to
> officially support?
I don’t know, it’s a Guix-specific hack, and just explaining the
rationale to GCC people may be tricky: they’ll think we’re all mad. ;-)
Ludo’.
next prev parent reply other threads:[~2018-03-21 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:47 bug#30820: Chunked store references in compiled code break grafting (again) Ludovic Courtès
2018-03-14 17:24 ` Ludovic Courtès
2018-03-16 8:54 ` bug#30395: " Ludovic Courtès
2018-03-20 23:07 ` Ludovic Courtès
2018-03-21 6:39 ` Ricardo Wurmus
2018-03-21 20:59 ` Ludovic Courtès [this message]
2018-03-19 21:22 ` Danny Milosavljevic
2018-03-19 22:29 ` Ludovic Courtès
2018-03-19 19:05 ` Mark H Weaver
2018-03-19 19:16 ` Mark H Weaver
2018-03-19 21:34 ` Danny Milosavljevic
2018-03-19 22:27 ` Ludovic Courtès
2018-03-20 1:04 ` Mark H Weaver
2018-03-20 8:50 ` Ludovic Courtès
2018-03-19 22:34 ` Ludovic Courtès
2018-03-20 0:52 ` Mark H Weaver
2018-03-20 8:56 ` Ludovic Courtès
2018-03-21 4:17 ` Mark H Weaver
2018-03-21 5:43 ` Mark H Weaver
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=87605pf8lg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30395-done@debbugs.gnu.org \
--cc=30820-done@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).