<div dir="ltr"><br><div class="gmail_quote">On Tue, Aug 11, 2009 at 1:19 AM, Duncan Coutts <span dir="ltr"><<a href="mailto:duncan.coutts@worc.ox.ac.uk">duncan.coutts@worc.ox.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Tue, 2009-08-04 at 07:07 +0300, Michael Snoyman wrote:<br>
> Hi all,<br>
><br>
> I've written a Yaml library built on top of libyaml (the same C<br>
> library at the core of Python's yaml library). All is well on my local<br>
> system and my server; I'm currently using it in production. However,<br>
> the build is failing on Hackage with the following build log:<br>
> <a href="http://hackage.haskell.org/packages/archive/yaml/0.0.1/logs/failure/ghc-6.10" target="_blank">http://hackage.haskell.org/packages/archive/yaml/0.0.1/logs/failure/ghc-6.10</a>.<br>
><br>
> It seems that whichever version of C2HS is installed on the server<br>
> does not allow "type" (or perhaps other keywords?) to be used as C<br>
> identifiers. Unfortunately, "type" is the name of a field in a C<br>
> struct I need to integrate with. It's obviously not vital that I get<br>
> it to compile on hackage, but 1) I'm worried this is a sign of a<br>
> bigger problem, and 2) it's always nice to have the API documentation<br>
> available online.<br>
><br>
> Any suggestions?<br>
<br>
</div></div>I recommend that you specify in the .cabal file the minimum version of<br>
c2hs that you require. It's probably 0.16 that you need.<br>
<br>
Then of course you'll probably find that the version of c2hs on the<br>
single build machine is indeed older than that. This shows us again the<br>
problem with using a single build machine rather than allowing any<br>
client to upload build reports. As an interim measure before we get the<br>
new hackage server, you could email Ross and ask him nicely to update<br>
c2hs on the build machine.<br>
<font color="#888888"><br>
Duncan</font></blockquote><div> </div></div>Thanks for getting back to me Duncan. I was in fact using 0.16 on my system. However, to simplify things, I went ahead and rewrote to use the FFI directly.<br><br>Michael<br></div>