Closed wz1000 closed 4 years ago
Is there a upstream issue and perfectly a patch (pull request) or other proof that it actually works?
I just built it with ghc-8.8.3
~/builds/data-accessor-template-0.2.1.16
❯ cabal new-build --allow-newer
Build profile: -w ghc-8.8.3 -O1
In order, the following will be built (use -v for more details):
- data-accessor-0.2.3 (lib:data-accessor) (requires build)
- utility-ht-0.0.15 (lib) (requires build)
- data-accessor-template-0.2.1.16 (lib:data-accessor-template) (first run)
Starting data-accessor-0.2.3 (all, legacy fallback)
Starting utility-ht-0.0.15 (lib)
Building data-accessor-0.2.3 (all, legacy fallback)
Building utility-ht-0.0.15 (lib)
Installing data-accessor-0.2.3 (all, legacy fallback)
Completed data-accessor-0.2.3 (all, legacy fallback)
Installing utility-ht-0.0.15 (lib)
Completed utility-ht-0.0.15 (lib)
Configuring data-accessor-template-0.2.1.16...
Preprocessing library for data-accessor-template-0.2.1.16..
Building library for data-accessor-template-0.2.1.16..
[1 of 2] Compiling Data.Accessor.Template ( src-2.11/Data/Accessor/Template.hs, /home/zubin/builds/data-accessor-template-0.2.1.16/dist-newstyle/build/x86_64-linux/ghc-8.8.3/data-accessor-template-0.2.1.16/build/Data/Accessor/Template.o )
[2 of 2] Compiling Data.Accessor.Template.Example ( src/Data/Accessor/Template/Example.hs, /home/zubin/builds/data-accessor-template-0.2.1.16/dist-newstyle/build/x86_64-linux/ghc-8.8.3/data-accessor-template-0.2.1.16/build/Data/Accessor/Template/Example.o )
cabal new-build --allow-newer 5.40s user 1.10s system 134% cpu 4.822 total
Additionally, see this comment on a issue from pandoc-crossref
, which transitively depends on data-accessor-template
Could it be relaxed to
< 2.16
?