unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: maximedevos@telenet.be
Cc: guix-devel@gnu.org
Subject: Question: wrap-program without #:sh can be ok even when cross-compiling?
Date: Sun, 06 Jun 2021 09:39:00 +0200	[thread overview]
Message-ID: <e731725c99624cb17fb301804a1bb09d8c7ff548.camel@student.tugraz.at> (raw)
In-Reply-To: ba0f3c036cf7e367b0cfb44842e178a7c937a880.camel@telenet.be

I think we might want to export a utility procedure
    (patch-shebangs files inputs)
so that files used during build (e.g. configure, Makefile, etc.) can do
(patch-shebangs build-stuff native-inputs) and the rest implicitly gets
(patch-shebangs files inputs) during the patch-shebangs phase.  WDYT?



             reply	other threads:[~2021-06-06  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06  7:39 Leo Prikler [this message]
2021-06-06 10:14 ` Maxime Devos
2021-06-06 10:57   ` Leo Prikler
  -- strict thread matches above, loose matches on Subject: below --
2021-06-05 18:39 Maxime Devos

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=e731725c99624cb17fb301804a1bb09d8c7ff548.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --subject='Re: Question: wrap-program without #:sh can be ok even when cross-compiling?' \
    /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

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 NNTP newsgroup(s).