Not really a bug report, but I was unsure where to post it. Just on a whim, I tried compiling and installing hugs on cygwin using the unix source tarball. Seems to work fine, including the ffi (with .so's rather then .dll's of course). 'wicked cool', as they say up here in new england. However, I havent really tested anything hard, just a simple ffi example (using a Ptr type and calling simple functions... ). Since I use msc most of the time anyway, this is a bit of wheel spinning on my part. Just curiousity. <* grin*>. The readme in the src/unix directory is a bit out of date, and talks about cygwin version beta 16 and 17. Things seem to work better then that file claims, but then again I don't think they are talking about using gcc like I did. Ron
Thanks for the report. Good to hear it's working on other platforms. (If you want to test Hugs a bit harder, follow the instructions in hugs98/tests/Readme.)
The readme in the src/unix directory is a bit out of date, and talks about cygwin version beta 16 and 17. Things seem to work better then that file claims, but then again I don't think they are talking about using gcc like I did.
Can you suggest some changes? I'm hoping that cygwin/gcc works pretty much the same as for Unix. What about Borland and MSVC? Can you provide updated config.h files for us to include in distributions? -- Alastair Reid alastair@reid-consulting-uk.ltd.uk Reid Consulting (UK) Limited http://www.reid-consulting-uk.ltd.uk/alastair/
I ran some the of the tests in hugs98/tests. They still suffer from the wrong exit code, so it is hard to tell what is going on. I ran some of the tests by hand in tests/ffi, and they seem fine. There is no real hard-core marshalling in there, so I will check that out by hand later. (i have some code I wrote for work that should do the trick) So.... so far cygwin works like any unix platform except for the problem with the exit codes. I dont know what is going on there. As for MSVC, I have been using that as my main development configuration, with no problems. Nice ! I did compile it once by hand (including files), but I never bothered to fully get everything working, as the msi install works great for me. As for BCC, I don't use this anymore, so I can't say. I sold out and bought MSVC. :) Cheers! Ron
As for MSVC, I have been using that as my main development configuration, with no problems. Nice ! I did compile it once by hand (including files), but I never bothered to fully get everything working, as the msi install works great for me. Please replace (including files) with (adding files to the visual studio
project by hand) Sorry :) Ron
I ran some of the tests by hand in tests/ffi, and they seem fine. There is no real hard-core marshalling in there, so I will check that out by hand later. (i have some code I wrote for work that should do the trick)
We would love to get more test cases. What we have at the moment is little more than a white box test of each feature I implemented - black box tests, more comprehensive tests and tests of the limits of the system would be especially valuable. We tend to swap back and forth with the GHC test suite so test cases would be especially valuable since they might flush out differences between the GHC and Hugs implementations.
So.... so far cygwin works like any unix platform except for the problem with the exit codes. I dont know what is going on there.
Hmmm, this sounds vaguely familiar. IIRC, there were some recent changes inside Hugs to avoid using 'system' on Windows platforms since it didn't do error codes correctly. Either we weren't thorough enough in applying these changes or we need to make them in the testing script as well (which is a piece of shell/perl script). -- Alastair Reid alastair@reid-consulting-uk.ltd.uk Reid Consulting (UK) Limited http://www.reid-consulting-uk.ltd.uk/alastair/
participants (2)
-
Alastair Reid -
R. Legere