Oh wow, this is becoming eerily similar to the failures aja@ is getting. Do dig more into this!
On Sat, Feb 17, 2024, 21:34 Evan Silberman <e...@jklol.net> wrote: > Evan Silberman <e...@jklol.net> wrote: > > Thanks to the amd64 snapshot package archives I was able to bisect to a > > working pandoc package on my machine. OK on 2024-01-16, NG on > > 2024-01-17. > > I guess what this means is my problem is traceable to the ghc 9.6.4 > bump. I have determined I can elicit a SIGILL reproducibly, outside of > the ports environment, when using ghc 9.6.4 to build unicode-collation > 0.1.3.6 (https://hackage.haskell.org/package/unicode-collation), e.g.: > > unicode-collation-0.1.3.6 $ cabal build > Resolving dependencies... > Build profile: -w ghc-9.6.4 -O1 > In order, the following will be built (use -v for more details): > - unicode-collation-0.1.3.6 (lib) (first run) > Configuring library for unicode-collation-0.1.3.6.. > Preprocessing library for unicode-collation-0.1.3.6.. > Building library for unicode-collation-0.1.3.6.. > [ 1 of 10] Compiling Text.Collate.Lang > [ 2 of 10] Compiling Text.Collate.Trie > [ 3 of 10] Compiling Text.Collate.UnicodeData > [ 4 of 10] Compiling Text.Collate.CanonicalCombiningClass > Error: cabal: Failed to build unicode-collation-0.1.3.6. The build > process > terminated with exit code -4 > > Same build is fine with ghc 9.2.7p5 from January. > > A little more messing around suggests that the issue is related to > Template Haskell. I might be able to generate a minimal reproducer. Stay > tuned? > > Evan >