
On 10/19/2014 07:29 PM, Brandon Allbery wrote:
On Sun, Oct 19, 2014 at 8:25 PM, Michael Martin
mailto:mmartin4242@gmail.com> wrote: As a Linux bigot myself, I'd say go with Linux. However, if you are more comfortable with OS X, I'm gonna guess that installing X Code (or whatever the compiler package is called these days) ought to make this one particular problem (header file not found) go away.
I'd guess otherwise, because "" in a #include (having peeked back at the original message) means it's a locally defined file, not a system header. That said, it doesn't rule out configure not having created it because it couldn't find some system header --- but the Command Line Tools should be sufficient for that.
Signals.h provides an interface to OS process signals, and should be provided by either the compiler package, or by the operating system itself. A quick google for "Mac OS/X Signals.h" tells me that this header file is, indeed, provided by the X-Code compiler package.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com mailto:allbery.b@gmail.com ballbery@sinenomine.net mailto:ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners