ack/plat/osx386 at 3fe285f8f8fcff0fd32de4c971400503d72158e0 - d0p1/ack - Cute Engineering : Cute solutions to hard problems

d0p1/ack

History

David Given c569ca15d8 Clean up how the language libraries refer to plat headers; they should be using the +pkg forms of the rules and getting the headers via the paths in descr, rather than depending on the +headers version.		2016-12-05 21:05:24 +01:00
..
include	Clean up how the language libraries refer to plat headers; they should be using	2016-12-05 21:05:24 +01:00
libsys	Clean up how the language libraries refer to plat headers; they should be using	2016-12-05 21:05:24 +01:00
boot.s	Fix my typo to put symbol "begrom" in correct section.	2016-11-19 19:23:42 -05:00
build-pkg.lua	Install only 1 copy, not 2 copies, of osx headers.	2016-11-08 17:13:51 -05:00
build-tools.lua	Commit a preview of osx386 and osxppc as new platforms.	2016-10-02 14:58:05 -04:00
descr	Teach cvmach to emit the symbol table.	2016-11-22 17:16:30 -05:00
README	Write README files for osx386 and osxppc.	2016-12-03 17:17:44 -05:00

README

The osx386 platform
===================

    ack -mosx386 ...

This platform produces Mach-o executables for Intel Mac OS X.  These
are 32-bit executables using our i386 code generator.

See ../osxppc/README, because our osx386 platform has many of the same
limitations and bugs as our osxppc platform.


Bugs
----

Some programs can't read the tty after using job control to suspend
and resume the program (with ^Z and "fg" in bash).  The read(2) system
call fails with EINTR.  In ACK's stdio (in libc), the error is sticky,
so all reads fail.  In Apple's stdio, the error is not sticky, and
only the next read fails.  The EINTR seems to happen only on Intel Mac
OS X, and not on other platforms.


George Koehler <xkernigh@netscape.net>
2016-12-03