From: Sam Ravnborg
Date: Fri, 7 Aug 2015 20:34:12 +0200
> From 7d8a508d74e6cacf0f2438286a959c3195a35a37 Mon Sep 17 00:00:00 2001
> From: Sam Ravnborg
> Date: Fri, 7 Aug 2015 20:26:12 +0200
> Subject: [PATCH] sparc64: use ENTRY/ENDPROC in VISsave
>
> Commit 44922150d87cef616fd183220d43d8fde4d413
> After 10 hours of building (my machine is probably not the fastest one),
> I can only confirm that the gold linker is still broken in
> binutils_2.25-11_sparc64.deb
>
>
I'm no developer. But I do have access to a T5120, where I could assign an
LDOM with 64 cores and 16gb of memory. If that would
On Fri, 2015-08-07 at 18:24 +0200, Artyom Tarasenko wrote:
> After 10 hours of building (my machine is probably not the fastest
> one),
> I can only confirm that the gold linker is still broken in
> binutils_2.25-11_sparc64.deb
Am I right, there are some fails / test error's, building binutils_2.
>From 7d8a508d74e6cacf0f2438286a959c3195a35a37 Mon Sep 17 00:00:00 2001
From: Sam Ravnborg
Date: Fri, 7 Aug 2015 20:26:12 +0200
Subject: [PATCH] sparc64: use ENTRY/ENDPROC in VISsave
Commit 44922150d87cef616fd183220d43d8fde4d41390
("sparc64: Fix userspace FPU register corruptions") left a
stale g
After 10 hours of building (my machine is probably not the fastest one),
I can only confirm that the gold linker is still broken in
binutils_2.25-11_sparc64.deb
Also I added
ifneq ($(findstring $(DEB_BUILD_ARCH), sparc),)
LD=ld
endif
to debian/rules (that's the only part of the patch reference
5 matches
Mail list logo