> I intend to work on getting Gforth ready for release in the next > weeks, and this will probably include testing on a MacOS X box, so the > next realease should work with just "configure; make" on MacOS X.
Wonderful! > Maybe I can even use a Windows box for testing (if Windows/Cygwin > yields to remote script-based testing without too much effort). Let me know if you need any help. It seems to be very Unix like, but it's m4 (and probably other tools) outputs DOS terminators. So, be careful there if prim is touched. I setup GForth with Unix terminators and hand wack the m4 output if that part is executed. > > I hadn't examined your scripts before, and I don't > understand why you are > > setting: > > > > env ac_cv_sizeof_long_long=0 > > > > Is there a problem I haven't discovered yet that this solves? > > This helps if gcc generates incorrect code for long longs (given the > number of platforms (SPARC, M68K, PPC) this has happened on, maybe we > should make this the default). How would I test if that is a problem? DaR --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
