all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: ‘strip’ phase
Date: Sat, 22 Nov 2014 12:53:46 +0100	[thread overview]
Message-ID: <87egsvjvsl.fsf@gnu.org> (raw)
In-Reply-To: <87oasxpp5k.fsf@yeeloong.lan> (Mark H. Weaver's message of "Mon, 27 Oct 2014 10:23:35 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> IMO, the best solution is to check for the presence of ELF headers
>>> ourselves.  We already have ELF code in Guile master.
>>
>> Yes, that sounds good.  Instead of relying on Guile’s ELF code, perhaps
>> it would be enough to check for the presence of the ELF magic bytes?
>
> Agreed.  The test need not be perfect, because the worst that can happen
> is an _occasional_ warning from 'strip', which really will be harmless :)

Commit 50b87bd in ‘core-updates’ does that.

Thanks,
Ludo’.

  reply	other threads:[~2014-11-22 11:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26 20:31 [PATCH] gnu: Add ruby 1.8.7 Pjotr Prins
2014-10-26 23:33 ` Mark H Weaver
2014-10-26 23:44   ` Pjotr Prins
2014-10-26 23:53     ` Pjotr Prins
2014-10-27  0:53       ` David Thompson
2014-10-27  1:44         ` Pjotr Prins
2014-10-27  1:43     ` Mark H Weaver
2014-10-27  1:56       ` Pjotr Prins
2014-10-27  4:11         ` Mark H Weaver
2014-10-27  9:05           ` ‘strip’ phase Ludovic Courtès
2014-10-27  9:28             ` Mark H Weaver
2014-10-27 12:16               ` Ludovic Courtès
2014-10-27 14:23                 ` Mark H Weaver
2014-11-22 11:53                   ` Ludovic Courtès [this message]
2014-10-27  5:17   ` [PATCH] gnu: Add ruby 1.8.7 Pjotr Prins

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=87egsvjvsl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.