[haskell-llvm] pushing llvm-base with patched setup.hs to hackage

Carter Schonwald carter.schonwald at gmail.com
Sat May 18 17:36:29 BST 2013


I will happily read any pull request made to address those concerns. If
these are a problem for you, please file bug tickets with known
reproducible failures.

Cheers
-Carter

On Saturday, May 18, 2013, Henning Thielemann wrote:

>
> On Fri, 17 May 2013, Carter Schonwald wrote:
>
>  if you need hugs support, please give us a patch that is of that cpp
>> style I've outlined that you've tested locally, as I and others don't have
>> access to hugs and i'm happy to help merge it in. In the mean time, I think
>> making sure that llvm bindings work on all current and near future haskell
>> platform releases takes priority over aesthetical arguments against so.
>>
>
> These are no aesthetical arguments, it's not about supporting especially
> Hugs, it's about having a reliable configure phase in general. I am
> concerned about adding more points of failure (hacks, TH) into the build
> procedure that was always broken, and becomes even more broken now. It all
> looks like the usual "I do not understand, what this code does, so let's
> build a wrapper around it, such that the case, that I am concerned with
> works for now and if people are not happy about it, they may add more
> wrappers". Does anyone of us understand how these configure.ac and
> Setup.hs work individually and work together? Would you please explain what
> the part of Setup.hs does, that you changed? Would you please explain how
> Cabal changed that makes the current current Setup.hs unusable? Since the
> current configure procedure is broken, there might be a way that 1) is not
> broken, 2) works for old and new Cabal and 3) works without hacks and
> Template Haskell.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://projects.haskell.org/pipermail/haskell-llvm/attachments/20130518/83ce6280/attachment.htm>


More information about the Haskell-llvm mailing list