Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

Ok so it seems to be a 64-bit symbol table (according to https://docs.oracle.com/cd/E53394_01/html/E54772/ar-3head.html): > A 64-bit archive symbol table sets ar_name to the string “/SYM64/”, padded with 9 blank characters to the right." We should skip it. I will make a patch. Thanks for the

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

Sylvain, I tried your patch, here's the output: cd "./th/T5976.run" && "/home/omer/haskell/ghc/inplace/test spaces/ghc-stage2" -c T5976.hs -dcore-lint -dcmm-lint -no-user-package-db -rtsopts -fno-warn-missed-specialisations -fshow-warning-groups -dno-debug-output -XTemplateHaskell -package

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

So I just tried validating on another system: > ghc git:(master) $ uname -a Linux linux-enrr.suse 4.1.34-33-default #1 SMP PREEMPT Thu Oct 20 08:03:29 UTC 2016 (fe18aba) x86_64 x86_64 x86_64 GNU/Linux > ghc git:(master) $ gcc --version gcc (SUSE Linux) 4.8.5 Copyright (C)

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

My bad, in fact we do. Could you try with the attached patch? It shows the failing filename in the archive. On 11/11/2016 17:18, Sylvain Henry wrote: It seems like we don't bypass the special filename "/" (symbol lookup table) in rts/Linker.c

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

Ah, sorry, that line was truncated. I posted the output here: https://gist.githubusercontent.com/osa1/ea72655b8369099e84a67e0949adca7e/raw/9e72cbfb859cb839f1898af39a46ff0896237d15/gistfile1.txt That line should be +ghc-iserv.bin: internal loadArchive: GNU-variant filename offset not found while

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

On Thu, Nov 10, 2016 at 11:12 PM, Ömer Sinan Ağacan wrote: > I'm trying to validate on a new system (not sure if related, but it has gcc > 6.2.1 and ld 2.27.0), and I'm having 177 unexpected failures, most (maybe > even > all) of them are similar to this one: > > =>

Re: 177 unexpected test failures on a new system -- is this yet another linker issue?

Ömer Sinan Ağacan writes: > I'm trying to validate on a new system (not sure if related, but it has gcc > 6.2.1 and ld 2.27.0), and I'm having 177 unexpected failures, most (maybe > even > all) of them are similar to this one: Hmm, I have a rather similar setup and yet I

177 unexpected test failures on a new system -- is this yet another linker issue?

I'm trying to validate on a new system (not sure if related, but it has gcc 6.2.1 and ld 2.27.0), and I'm having 177 unexpected failures, most (maybe even all) of them are similar to this one: => T5976(ext-interp) 1 of 1 [0, 0, 0] cd "./th/T5976.run" &&