Opened 9 years ago

Closed 9 years ago

Last modified 44 years ago

#465 closed bug (Wont Fix)

in hdirect stdcall not supported on PPC Mac OS X 10.3

Reported by: yaseppochi Owned by: nobody
Priority: normal Milestone:
Component: Build System Version: None
Keywords: Cc:
Operating System: Architecture:
Type of failure: Difficulty:
Test Case: Blocked By:
Blocking: Related Tickets:

Description

I'm building CVS HEAD from 2005-10-05 with 6.4.1.

I get the error in the attached log.

I'm not in a hurry, but in a couple of months one of my
projects will be to the point that I would like to call
some Haskell code from another project written in C. 
If there's anything I can  do to help with getting
hdirect supported on

Mac PowerBook G4
Mac OS X 10.3.9 "panther"

Please let me know.  (I probably will upgrade to 10.4
"Tiger" in the near future.)

It would be nice if the build could fail safely (ie,
not produce the hdirect library, but not stop the rest
of the fptools build).  There doesn't seem to be a way
to disable the feature via configure.

Stephen Turnbull
stephen@xemacs.org

Attachments (1)

bug.2.log (2.4 KB) - added by yaseppochi 9 years ago.

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by yaseppochi

comment:1 Changed 9 years ago by simonmar

Logged In: YES 
user_id=48280

This isn't an authoritative answer, but it is likely to be
the case that H/Direct has never been ported to MacOS X, and
H/Direct is not being actively maintained at the moment.

Why do you need H/Direct?  If you just need to call Haskell
from C, there are a variety of ways to achieve that, with
and without extra tools.

comment:2 Changed 9 years ago by yaseppochi

Logged In: YES 
user_id=88738

Thanks for the quick reply.

I don't need HDirect specifically.  I may want to call
Haskell code from XEmacs, someday.  I checked out fptools
from CVS, the build broke in hdirect/lib, I looked to see if
I needed it.  Its docs claim to be the "way of the future"
in Haskell FFI, so I concluded (a) I don't need it now and
(b) I will very likely want (something like) it in the future.

I reported this because "cvs checkout fptools; cd fptools;
./configure; make" seems like a pretty natural approach with
a half-dozen prerequisite projects, and the build apparently
breaks.  (I wonder if make install would work, that probably
chokes in the same place.)

comment:3 Changed 9 years ago by simonmar

  • Status changed from assigned to closed
Logged In: YES 
user_id=48280

Ah.  You don't want to check out the whole of fptools.  Take
a look at the CVS cheat sheet here:

http://www.haskell.org/ghc/docs/latest/html/building/sec-cvs.html
Note: See TracTickets for help on using tickets.