Re: [racket-dev] racket 6.3 build failures on armel
David Bremner <david@tethera.net> writes:
> The porterbox is easy, and attached. The autobuilder is a bit more work,
> but I can do it if the porterbox values don't suggest anything to try
> (it would somehow be more efficient to try an experimental patch and get
> the preprocessor values at the same time)
A helpful sysadmin (hi pabs!) ran the command on the autobuilder as well, and got
_almost_ the same output.
It most likely is significant that the gcc version is different. I'll
try upgrading the porterbox chroot and see if it duplicates the
autobuilder failure.
--- abel.txt 2015-12-11 11:22:53.794883202 -0400
+++ 343324 2015-12-11 11:19:12.565432819 -0400
@@ -165,7 +165,7 @@
#define __SFRACT_MIN__ (-0.5HR-0.5HR)
#define __UTQ_FBIT__ 128
#define __FLT_MANT_DIG__ 24
-#define __VERSION__ "5.2.1 20151125"
+#define __VERSION__ "5.3.1 20151207"
#define __UINT64_C(c) c ## ULL
#define __ULLFRACT_FBIT__ 64
#define __FRACT_EPSILON__ 0x1P-15R
@@ -315,7 +315,7 @@
#define __INTMAX_TYPE__ long long int
#define __DEC128_MAX_EXP__ 6145
#define __ATOMIC_CONSUME 1
-#define __GNUC_MINOR__ 2
+#define __GNUC_MINOR__ 3
#define __UINTMAX_MAX__ 0xffffffffffffffffULL
#define __DEC32_MANT_DIG__ 7
#define __HA_FBIT__ 7
Reply to: