GNU bug report logs - #54304
[PATCH] Don't fix git executable location during Elixir build

Previous Next

Full log

Message #47 received at 54304 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Cees de Groot <cg <at> evrl.com>
Cc: 54304 <at> debbugs.gnu.org, Tobias Geerinckx-Rice <me <at> tobias.gr>,
 Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#54304: [PATCH] Don't fix git executable location during
 Elixir build
Date: Fri, 11 Mar 2022 22:51:59 +0100

Hi,

Cees de Groot <cg <at> evrl.com> skribis:

> On Wednesday, March 9th, 2022 at 16:49, Tobias Geerinckx-Rice <me <at> tobias.gr> wrote:
>> If BEAM somehow obfuscates store references we'll have to find a similar work-around to stop it. Let us know what you find.
>>
> Yup. BEAM files have literals stored in a single Deflated blob (https://beam-wisdoms.clau.se/en/latest/indepth-beam-file.html). So the scanning won't work.

If we know what set of store references go in those blogs, we could
create a text file or something in #$output whose sole purpose is to
keep a reference to those store items.

For example, if we know those BEAM files contain a reference to Git, we
can add a phase like:

  (lambda* (#:key inputs outputs #:allow-other-keys)
    (symlink (search-input-file inputs "git")
             (string-append (assoc-ref output "out")
                            "/libexec/elixir/.git")))

That way the GC will keep Git around.

Thoughts?

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.