
Thanks Alexander.. Here's the shocker: I just checked that page again ( http://hackage.haskell.org/package/sbv) and now it's mysteriously fine! Hackage must've recompiled the package somehow. Someone watching this thread must've fixed something on the server and triggered a new compile. While I'm happy the problem is now gone, the mystery behind the hackage recompile remains.. Maybe someone can shed some light on how hackage goes about managing the uploads. -Levent. On Tue, Jul 17, 2012 at 9:43 AM, Alexander Foremny < alexanderforemny@gmail.com> wrote:
Dear Levent,
unfortunately I am at a loss here. As far as I understand it this should be fixed in QuickCheck's .cabal file or on Hackage. But I am not experienced enough to decide.
You best wait for someone else to comment on this. Depending on template-haskell in your .cabal file is not the way to go as far as I understand it. But maybe it's a possible work-around in case you depend on the package being available on Hackage timely.
Regards, Alexander Foremny
It builds fine locally on my box; but not on hackage. Here's the page: http://hackage.haskell.org/package/sbv-2.2
Thanks for looking into this Alexander, I appreciate your help.
-Levent.
On Tue, Jul 17, 2012 at 9:09 AM, Alexander Foremny
wrote: Which package are you trying to build? Is it a local package that fails to build or something on Hackage? Its .cabal file or at least full dependencies would be of interest.
Regards, Alexander Foremny
2012/7/17 Levent Erkok
: Thanks Alexander. However, I'm not sure how to use the workaround described so I can get hackage to properly compile my package. It sounds like I have to add a "template-haskell >= 2.7.0.0" dependency to my own cabal
file,
which sounds like the wrong thing to do in the long-run.
Is there something that can be done on the hackage/ghc side to avoid this issue? Or something less drastic than adding a template-haskell dependency on my own package's cabal file?
Thanks,
-Levent.
On Tue, Jul 17, 2012 at 7:31 AM, Alexander Foremny
wrote: Dear Levent,
I think this [1] could be related.
Regards, Alexander Foremny
PS. Sent this to Levent directly. Here's a copy for the mailing list. Sorry for the noise.
[1]
http://haskell.1045720.n5.nabble.com/Bad-interface-problem-td5714184.html
---------- Forwarded message ---------- From: Alexander Foremny
Date: 2012/7/17 Subject: Re: [Haskell-cafe] hackage compile failure with QuickCheck 2.5
To: Levent Erkok
Dear Levent,
I think this [1] could be related.
Regards, Alexander Foremny
[1]
http://haskell.1045720.n5.nabble.com/Bad-interface-problem-td5714184.html
2012/7/17 Levent Erkok
: [This message is more appropriate for a hackage mailing list I presume, but that doesn't seem to exist. Let me know if there's a better place
to
send it.]
I'm having a hackage compile failure for a newly uplodaded package that has a QuickCheck 2.5 dependence. The error message is:
[13 of 13] Compiling Test.QuickCheck.All ( Test/QuickCheck/All.hs, dist/build/Test/QuickCheck/All.o )
Test/QuickCheck/All.hs:15:1: Bad interface file:
/usr/local/tmp/archive/install/lib/template-haskell-2.6.0.0/ghc-7.4.1/Language/Haskell/TH.hi
Something is amiss; requested module template-haskell-2.6.0.0:Language.Haskell.TH differs from name
found
in the interface file template-haskell:Language.Haskell.TH
The full log file is at (search for "Something is a miss" in it):
http://hackage.haskell.org/packages/archive/sbv/2.2/logs/failure/ghc-7.4
Needless to say, I don't see this problem when I compile this
at home with the same compiler (ghc 7.4.1) as hackage is using; also Hackage has a successfully compiled QuickCheck 2.5 package.
Could it be something related to the particular cabal/ghc installation on the hackage server? In particular, I don't understand why it picks template-haskell 2.6.0.0 when there's a newer version (2.7.0.0). As far as I can see, QuickCheck doesn't put an upper limit on its template haskell version dependency.
I'd appreciate any pointers with this. (Googling and questions on
2012/7/17 Levent Erkok
: package the #haskell irc channel didn't help much, unfortunately.)
-Levent.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe