From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:39572) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqRlE-0005IH-9e for guix-patches@gnu.org; Sun, 03 Feb 2019 19:05:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gqRgC-0001f6-Nr for guix-patches@gnu.org; Sun, 03 Feb 2019 19:00:06 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:58636) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gqRgA-0001b5-Un for guix-patches@gnu.org; Sun, 03 Feb 2019 19:00:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gqRgA-0004ZW-Kf for guix-patches@gnu.org; Sun, 03 Feb 2019 19:00:02 -0500 Subject: [bug#34304] [PATCH] doc: Document how to enable qemu binfmt service and how to use it. Resent-Message-ID: From: Ricardo Wurmus References: <20190203154601.32098-1-dannym@scratchpost.org> Date: Mon, 04 Feb 2019 00:59:08 +0100 In-Reply-To: <20190203154601.32098-1-dannym@scratchpost.org> (Danny Milosavljevic's message of "Sun, 3 Feb 2019 16:46:01 +0100") Message-ID: <87d0o8whir.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Danny Milosavljevic Cc: 34304@debbugs.gnu.org Danny Milosavljevic writes: > * doc/contributing.texi (Submitting Patches): Document how to enable qemu > binfmt service and how to use it. Sounds good to me! > +We recommend you also try to build the package on other platforms. We > +do not presume that you have all the platforms, therefore we recommend > +using the qemu binfmt service of GuixSD. In order to enable it, add > +the following service to your operating-system configuration's services: How about this: --8<---------------cut here---------------start------------->8--- We recommend you also try building the package on other supported platforms. As you may not have access to actual hardware platforms, we recommend using the @code{qemu-binfmt-service-type} to emulate them. In order to enable it, add the following service to the list of services in your @code{operating-system} configuration: --8<---------------cut here---------------end--------------->8--- > +You can then build packages like the following, respectively: > +@example > +guix build --system=3Darmhf-linux --rounds=3D2 my-package > +guix build --system=3Daarch64-linux --rounds=3D2 my-package > +guix build --system=3Dpowerpc-linux --rounds=3D2 my-package > +guix build --system=3Dmips64el-linux --rounds=3D2 my-package > +@end example How about: --8<---------------cut here---------------start------------->8--- You can then build packages for different platforms by specifying the @code{--system} option. For example, to build the =E2=80=9Chello=E2=80=9D = package for the armhf, aarch64, powerpc, or mips64 architectures, you would run the following commands, respectively: @example guix build --system=3Darmhf-linux --rounds=3D2 hello guix build --system=3Daarch64-linux --rounds=3D2 hello guix build --system=3Dpowerpc-linux --rounds=3D2 hello guix build --system=3Dmips64el-linux --rounds=3D2 hello @end example --8<---------------cut here---------------end--------------->8---