2010/1/17 Mark Lentczner ma...@glyphic.com:
AHA!
Note that after running cabal haddock we re-build all of our .hi and
.o files EXCEPT ./dist/build/HSsyb-with-class-0.6.1.o
And now, since TH generates random symbols, we have symbols in the new
.hi files that aren't in the old (and only)
=== Short Story ===
If I build syb-with-class-0.6 via cabal (cabal configure; cabal build) in the
unpacked tar directory, it builds correctly.
If I build it via cabal install (either from the unpacked directory, or by
letting cabal fetch it), then the resulting package is corrupted. In
This sounds similar to an issue I was seeing over here:
http://groups.google.com/group/happs/msg/04ecfe4fd6285c0d
The module being compiled also includes TH top-level statements, and
was only reproducible when building from Cabal.
Here's another occurance on a different platform:
Indeed - all those look exactly like the same issue.
And the workaround:
http://groups.google.com/group/happs/msg/1e7761d421b0e5eb
That doesn't fix the real issue: It causes happstack-data to not need the thing
that is built wrong in syb-with-class. I believe my work-around (build
2010/1/16 Mark Lentczner ma...@glyphic.com:
Indeed - all those look exactly like the same issue.
And the workaround:
http://groups.google.com/group/happs/msg/1e7761d421b0e5eb
That doesn't fix the real issue: It causes happstack-data to not need the
thing that is built wrong in
AHA!
Note that after running cabal haddock we re-build all of our .hi and
.o files EXCEPT ./dist/build/HSsyb-with-class-0.6.1.o
And now, since TH generates random symbols, we have symbols in the new
.hi files that aren't in the old (and only) HSsyb-with-class-0.6.1.o.
So, this leaves us
