From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56106) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drhzE-0003YL-2V for guix-patches@gnu.org; Tue, 12 Sep 2017 06:00:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drhz9-0006cb-9G for guix-patches@gnu.org; Tue, 12 Sep 2017 06:00:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:54328) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1drhz9-0006cK-4n for guix-patches@gnu.org; Tue, 12 Sep 2017 06:00:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1drhz8-0001MT-JY for guix-patches@gnu.org; Tue, 12 Sep 2017 06:00:02 -0400 Subject: [bug#28226] Build go with gccgo Resent-Message-ID: MIME-Version: 1.0 In-Reply-To: <20170824205146.GM2484@macbook42.flashner.co.il> References: <20170824205146.GM2484@macbook42.flashner.co.il> From: Catonano Date: Tue, 12 Sep 2017 11:59:31 +0200 Message-ID: Content-Type: multipart/alternative; boundary="f403045c199086bb400558fb1948" 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: Efraim Flashner Cc: 28226@debbugs.gnu.org --f403045c199086bb400558fb1948 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2017-08-24 22:51 GMT+02:00 Efraim Flashner : > I need some help testing this on x86_64, I did all the building and > testing on aarch64. It turns out there's a known issues in the cgo > implementation that causes the test suite to fail on aarch64. With this > patch set I was able to build gccgo@7 -> go@1.7 -> lfam's syncthing. > I can't apply these patches ~/projects/guix$ git am 0001-gnu-custom-gcc-Add-flag-to-optionally-not-remove-con.patch Applying: gnu: custom-gcc: Add flag to optionally not remove conflicting files. ~/projects/guix$ git am 0002-gnu-Add-gccgo-7.patch Applying: gnu: Add gccgo@7. error: patch non riuscita: gnu/packages/gcc.scm:414 error: gnu/packages/gcc.scm: la patch non pu=C3=B2 essere applicata Patch failed at 0001 gnu: Add gccgo@7. The copy of the patch that failed is found in: .git/rebase-apply/patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort". I don't know what these patches do, I was just trying to apply them in order (1, 2, 3) Should I follow a different order ? I would have attempted to build this thing I git pulled on master right now ( 12 september) and created a branch for thhese patches and git am'ed there --f403045c199086bb400558fb1948 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2017-08-24 22:51 GMT+02:00 Efraim Flashner <efraim@fl= ashner.co.il>:
I need some help testing this on = x86_64, I did all the building and
testing on aarch64. It turns out there's a known issues in the cgo
implementation that causes the test suite to fail on aarch64. With this
patch set I was able to build gccgo@7 -> go@1.7 -> lfam's syncthi= ng.

I can't = apply these patches

~/projects/guix$ git am 0001-gnu-custom-gcc-Add-= flag-to-optionally-not-remove-con.patch
Applying: gnu: custom-gcc: Add f= lag to optionally not remove conflicting files.

~/projects/guix$ git= am 0002-gnu-Add-gccgo-7.patch
Applying: gnu: Add gccgo@7.
error: pat= ch non riuscita: gnu/packages/gcc.scm:414
error: gnu/packages/gcc.scm: l= a patch non pu=C3=B2 essere applicata
Patch failed at 0001 gnu: Add gccg= o@7.
The copy of the patch that failed is found in: .git/rebase-apply/pa= tch
When you have resolved this problem, run "git am --continue&quo= t;.
If you prefer to skip this patch, run "git am --skip" inst= ead.
To restore the original branch and stop patching, run "git am = --abort".


I don't know what these patches do= , I was just trying to apply them in order (1, 2, 3)

Sho= uld I follow a different order ?

I would have attempted t= o build this thing

I git pulled on master right now ( 12 = september) and created a branch for thhese patches and git am'ed there<= br>

--f403045c199086bb400558fb1948--