#include "string.h" on mac

[ozgurakgun]

#include "string.h" on my system gives the following error:

c2hs: C header contains errors:

/usr/include/string.h:131: (column 90) [ERROR]  >>> Syntax error !
  The symbol `=' does not fit here.

I am on Mac OS X Mavericks.

The relevant line in string.h on this machine is the following:

char    *stpncpy(char *, const char *, size_t) __OSX_AVAILABLE_STARTING(__MAC_10_7, __IPHONE_4_3);

I am not sure what __IPHONE_4_3 expands to, but I can investigate if you think it can be helpful.

Thanks!

[ian-ross]

Do you think you could try this with C2HS HEAD? I fixed a problem that might be causing this after the last release to Hackage (c68d900). If that does fix this, I'll make a new release right away.

[ian-ross]

Could you tell me which version of C2HS you're using? Just paste the output of "c2hs --version" on your system into a comment.

[ccarter]

I'm having this same issue. I tried compiling from head and have same issue. Here is --version. Date seems wrong but I'm pretty sure I did it correctly.

C->Haskell Compiler, version 0.17.2 Crystal Seed, 24 Jan 2009
build platform is "x86_64-darwin" <1, True, True, 1>

[ian-ross]

@ozgurakgun @ccarter OK, this is tricky. I don't have a Mac to test/debug on. I've been looking around for a virtualisation option ("EC2 for MacOS"), but haven't found anything cheap/flexible enough yet. Unless one of you wants to try to fix this, it's going to take a while, until I've found a hosting option I can use.

[ccarter]

Can you give me some pointers on where to look and how to get the value out of the __OSX_AVAILABLE_STARTING macro. I'm not much of a c hacker, but this is causing me fits so I'll try to help.

[ian-ross]

@ccarter I'm trying to work out a way to get access to a Mac for fixing this sort of thing. However, if you really do want to try to fix this, I'd probably start by running C2HS on a relevant minimal test case with "C traversal" debug output ("-d ctrav" option) to see exactly what's going on when C2HS reads the headers, then I'd try to get a look at what those macros expand to by running the C compiler over them (for GCC, this is the "-E" option). After that, I'd have to start looking around in the C2HS code.

[mietek]

I have included the relevant macros in #85. Sorry for the duplication.

[ian-ross]

See recent comments on #85. Closing as duplicate of #85.