all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: %static-inputs: Use bash from PATH in bootstrap tar.
Date: Wed, 19 Oct 2016 20:00:39 +0000	[thread overview]
Message-ID: <4600E3C3-92CE-45AA-9CED-154948D6218B@flashner.co.il> (raw)
In-Reply-To: <87k2d45ddw.fsf@gnu.org>



On October 19, 2016 10:48:11 PM GMT+03:00, ludo@gnu.org wrote:
>Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On Wed, Oct 19, 2016 at 05:34:17PM +0200, Ludovic Courtès wrote:
>>> csanchezdll@gmail.com (Carlos Sánchez de La Lama) skribis:
>>> 
>>> > See
>>> >
><http://lists.gnu.org/archive/html/guix-devel/2016-09/msg02272.html>.
>>> 
>>> Could you put this URL next to the “Do not use /bin/sh” comment?
>>> 
>>> > gnu/packages/make-bootstrap.scm (%static-inputs): Use bash from
>PATH.
>>> 
>>> Otherwise LGTM, thanks!
>>> 
>>> Ludo’.
>>> 
>>
>> Was this tested with the other bootstrap binaries?
>
>It changes execv("/bin/sh", …) to execvp("sh", …) so it looks right.
>
>> I'm still having trouble with the aarch64 ones, didn't check if/how
>it
>> affected the ones that are already in Guix (which I assume would be
>> not at all)
>
>What kind of problems?  After this patch?
>
>Thanks,
>Ludo’.

Sorry, unrelated to this patch. Nvm and carry on

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2016-10-19 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 15:55 [PATCH] gnu: %static-inputs: Use bash from PATH in bootstrap tar Carlos Sánchez de La Lama
2016-10-19 15:34 ` Ludovic Courtès
2016-10-19 17:13   ` Efraim Flashner
2016-10-19 19:48     ` Ludovic Courtès
2016-10-19 20:00       ` Efraim Flashner [this message]
2016-10-24  6:59   ` Carlos Sánchez de La Lama
2016-10-24 21:08     ` Ludovic Courtès
2016-10-25  7:33       ` Carlos Sánchez de La Lama

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=4600E3C3-92CE-45AA-9CED-154948D6218B@flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 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.