On Sun, Jun 25, 2017 at 08:42:17 -0600, Anthony Fok wrote:
> On Sat, Jun 24, 2017 at 2:58 PM, Aurelien Jarno wrote:
> > On 2017-06-24 11:15, Anthony Fok wrote:
> >> Or, better yet, is there a way to find out what went wrong on
> >> zemlinsky? Is it an older machine with an
On 06/25/2017 04:42 PM, Anthony Fok wrote:
>>> Or, better yet, is there a way to find out what went wrong on
>>> zemlinsky? Is it an older machine with an older CPU that does not
>>> support some newer CPU instructions? (Sorry, I know nothing about
>>> s390x and I am likely completely wrong.)
>>
On Sat, Jun 24, 2017 at 2:58 PM, Aurelien Jarno wrote:
> On 2017-06-24 11:15, Anthony Fok wrote:
>> There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
>> for s390x on zemlinsky.
>>
>> Seeing the logs at
>>
>>
On 2017-06-24 11:15, Anthony Fok wrote:
> Hello,
>
> There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
> for s390x on zemlinsky.
>
> Seeing the logs at
>
> https://buildd.debian.org/status/logs.php?pkg=golang-1.8=s390x
>
> It seems that zemlinsky fails consistently
Hello,
There seems to be a hiccup when golang-1.8 (1.8.3-1) was last built
for s390x on zemlinsky.
Seeing the logs at
https://buildd.debian.org/status/logs.php?pkg=golang-1.8=s390x
It seems that zemlinsky fails consistently "Illegal Instruction" early
in the build,
while both zandonai and