From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: Texlive and native-inputs Date: Wed, 29 Oct 2014 20:55:55 +0100 Message-ID: <20141029195555.GA8268@jocasta.intra> References: <20141029165958.GA4944@debian.eduroam.u-bordeaux.fr> <20141029171309.GA30858@jocasta.intra> <20141029173948.GA16948@debian.eduroam.u-bordeaux.fr> <20141029185144.GA27092@debian> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjZLm-0007cS-79 for guix-devel@gnu.org; Wed, 29 Oct 2014 15:56:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjZLh-0005LN-Nt for guix-devel@gnu.org; Wed, 29 Oct 2014 15:56:10 -0400 Received: from de.cellform.com ([88.217.224.109]:44509 helo=jocasta.intra) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjZLh-0005LJ-8d for guix-devel@gnu.org; Wed, 29 Oct 2014 15:56:05 -0400 Content-Disposition: inline In-Reply-To: <20141029185144.GA27092@debian> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Andreas Enge Cc: guix-devel@gnu.org --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 29, 2014 at 07:51:44PM +0100, Andreas Enge wrote: 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 proc= ess. > Is this distinguished somehow? (Well, there is of course the problem= of > scripts that are used during the build process _and_ installed on th= e user's > machine, which means that the package is simply not cross-compilable= in > our setting. =20 In a sense this is what happens with texlive. "make check" uses perl s= cripts, and other perl scripts are installed. =20 But then I suppose that "make check" does not make much sense anyway w= hen cross-compiling? Do we activate it then? Supposing it was possible to run "make check" on a cross-compiled build (fo= r=20 example using an emulator), then we would need the non-native perl. The installed perl scripts also need the non-native perl. =20 So it looks as if the the native perl is not needed at all. =20 What do these scripts do anyway? Are they fundamental to TeXlive or are th= ey for some bells and whistles? J' --=20 PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRRRkoACgkQimdxnC3oJ7MyzgCcDfmIGkkKHuopvDAmJXI3trHd WngAn18mF0nQghXxfGY9ittrGrrhvktk =zsX/ -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY--