all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Texlive and native-inputs
Date: Wed, 29 Oct 2014 19:51:44 +0100	[thread overview]
Message-ID: <20141029185144.GA27092@debian> (raw)
In-Reply-To: <20141029173948.GA16948@debian.eduroam.u-bordeaux.fr>

On Wed, Oct 29, 2014 at 06:39:48PM +0100, Andreas Enge wrote:
> Would it work? One would need to patch-shebang with the normal input and
> use the native-input for scripts that are used during the build process.
> Is this distinguished somehow? (Well, there is of course the problem of
> scripts that are used during the build process _and_ installed on the user's
> machine, which means that the package is simply not cross-compilable in
> our setting.

In a sense this is what happens with texlive. "make check" uses perl scripts,
and other perl scripts are installed.

But then I suppose that "make check" does not make much sense anyway when
cross-compiling? Do we activate it then?

Andreas

  parent reply	other threads:[~2014-10-29 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 17:00 Texlive and native-inputs Andreas Enge
2014-10-29 17:13 ` John Darrington
2014-10-29 17:39   ` Andreas Enge
2014-10-29 17:52     ` John Darrington
2014-10-29 18:51     ` Andreas Enge [this message]
2014-10-29 19:55       ` John Darrington
2014-10-29 22:31         ` Andreas Enge
2014-10-30  7:53           ` John Darrington
2014-10-30  8:02             ` Andreas Enge
2014-10-30  9:24               ` John Darrington
2014-10-29 22:37       ` Ludovic Courtès
2014-10-29 22:29     ` Ludovic Courtès
2014-10-29 17:43   ` Andreas Enge
2014-10-29 18:03     ` John Darrington

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=20141029185144.GA27092@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.