From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: Should python-build-system packages have native-inputs? Date: Sat, 28 Apr 2018 12:22:53 -0700 Message-ID: <87y3h7kueq.fsf@gmail.com> References: <874ljv7rk0.fsf@gmail.com> <9766df40-5e91-577e-d2ed-195a1d8569fd@crazy-compilers.com> <87muxn63p9.fsf@gmail.com> <0e4db36b-cc7b-588b-1f37-bc5ce5bae2ab@crazy-compilers.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53833) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCVR0-0000lz-QZ for guix-devel@gnu.org; Sat, 28 Apr 2018 15:23:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fCVQz-0004SJ-Hn for guix-devel@gnu.org; Sat, 28 Apr 2018 15:23:02 -0400 Received: from mail-pf0-x22c.google.com ([2607:f8b0:400e:c00::22c]:34151) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fCVQz-0004Ru-A7 for guix-devel@gnu.org; Sat, 28 Apr 2018 15:23:01 -0400 Received: by mail-pf0-x22c.google.com with SMTP id a14so3876431pfi.1 for ; Sat, 28 Apr 2018 12:23:01 -0700 (PDT) In-Reply-To: <0e4db36b-cc7b-588b-1f37-bc5ce5bae2ab@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 28 Apr 2018 13:25:11 +0200") 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" To: Hartmut Goebel Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hartmut Goebel writes: >> the python-build-system does not cross-compile. > > In any case, this is a current limitation only :-) I see. If we actually do plan on implementing some kind of cross-compilation support for the python-build-system, then I can understand why it makes sense to proactively put into the native-inputs those things which might possibly need to be native-inputs when that time comes. Can we at least mention in the manual that the python-build-system doesn't currently cross-compile, so native-inputs will be treated the same as inputs for now, but we still recommend putting the "build-only dependencies" in native-inputs in order to future-proof our package definitions? That alone would have helped clarify things for me when I was starting out. After reading about Python extension modules a little more, it seems that they can in fact be cross-compiled. I didn't look into Python 2, and I don't know what it would take to enable such cross-compilation in the python-build-system. For those following along, here are some related links. An explanation of Python extension modules: https://docs.python.org/3/extending/building.html#distributing-your-extensi= on-modules Some Python open bugs that mention cross-compilation: https://bugs.python.org/issue?%40columns=3Did%2Cactivity%2Ctitle%2Ccreator%= 2Cassignee%2Cstatus&%40sort=3D-activity&%40group=3Dpriority&%40filter=3Dsta= tus&status=3D-1%2C1%2C3&%40search_text=3Dcross-compile&submit=3Dsearch+in+o= pen+issues =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlrkyg4ACgkQ3UCaFdgi Rp3q1w/+L2mrLKFuDAlAqsemgZBWhzKPVTv1vgLXjsvzoRUsVSoSSgGPWyQYLPQx WT6kMb0rh5MjS5sQVyVWE827UNkgBMlu9K2dRb+kqmZ6SUD6+n6wKaHtJi4qJ865 XLW2s2r+576Yxwk2W/6HtCswWheTOfzjw6xHVAZZQyF+ISXG8q5NpwCsUtu4LghL ugIOwvYSsS+RTsURH2O9ziv9q6nNG97PwWQy0AC6B3Dq9xjvGIQjuU+WSco5l0ah 2hdc1FBgQxBosT9V2Zy16wshH9+GBjL7QBR5VhAsY7MCh8/zebl4mE40vei5XP3J eDiLtkVqMLFi+vBoW3SckVzSpZ9J96LQdGxNrf5JzeP8itTAJRZpCE+BcH8JcQ/l JC0SDtvhSvhnr2oGBShk31TKtQTwg1e5tXo7zU/GH1ElJSy0az1H/pI0WThM6BRp eYwK5CdYSF1+zo240LGwmZkhe3LJQZsEOr/Aj2752oHoUkuEREF6Yk86iYZdYnEU 0HCOy/hJRTNKKcRjtD0Kcd8nW9+kdAuursLJwA2+HZnz0pF5ZyN4x/bo1DpgUQbR rmwkJSxCUmP/MUADIpR2fskS1e97YYESLIymiUkWQdXdDXEJfVTOA7PNxhNGDhkc ZjH5doLA9ZwrLyB+75KJotVqLTBZZs5xn3NPBXxArvHF6jdiCGU= =g0Pd -----END PGP SIGNATURE----- --=-=-=--