
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
https://en.wikipedia.org/wiki/Ar_(Unix)#System_V_.28or_GNU.29_variant
On 11/11/2016 16:49, Ömer Sinan Ağacan wrote:
Ah, sorry, that line was truncated. I posted the output here: https://gist.githubusercontent.com/osa1/ea72655b8369099e84a67e0949adca7e/raw...
That line should be +ghc-iserv.bin: internal loadArchive: GNU-variant filename offset not found while reading filename from `/home/omer/haskell/ghc/libraries/ghc-prim/dist-install/build/libHSghc-prim-0.5.0.0.a' + (GHC version 8.1.20161107 for x86_64_unknown_linux) + Please report this as a GHC bug:http://www.haskell.org/ghc/reportabug
2016-11-11 0:52 GMT-05:00 Reid Barton
mailto:rwbarton@gmail.com>: On Thu, Nov 10, 2016 at 11:12 PM, Ömer Sinan Ağacan
mailto:omeragacan@gmail.com> 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: > > =====> T5976(ext-interp) 1 of 1 [0, 0, 0] > cd "./th/T5976.run" && "/home/omer/haskell/ghc/inplace/test > spaces/ghc-stage2" -c T5976.hs -dcore-dno-debug-output -XTemplateHaskell > -package template-haskell -fexternal-interpreter -v0 > Actual stderr output differs from expected: > --- ./th/T5976.run/T5976.stderr.normalised 2016-11-10 > 23:01:39.351997560 -0500 > +++ ./th/T5976.run/T5976.comp.stderr.normalised 2016-11-10 > 23:01:39.351997560 -0500 > @@ -1,7 +1,4 @@ > - > -T5976.hs:1:1: > - Exception when trying to run compile-time code: > - bar > -CallStack (from HasCallStack): > - error, called at T5976.hs:<line>:<column> in <package-id>:Main > - Code: error ((++) "foo " error "bar") > +ghc-iserv.bin: internal loadArchive: GNU-variant filename offset not > found while reading filename f Did this line get truncated? It might help to have the rest of it.
Regards, Reid Barton
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs