ack/plat/linux386
2016-08-14 11:23:57 +02:00
..
include Wasn't exporting the plat headers; refactor to make this a little cleaner. 2016-08-14 11:01:36 +02:00
libsys Turns out I wasn't building the syscall libraries. Do so. 2016-08-14 11:23:57 +02:00
.distr Update distribution files. 2013-05-15 23:46:15 +01:00
boot.s Ensured that _errno is always defined. Rejigged the pc86 boot code so it doesn't always waste 510 bytes of memory. 2007-04-24 19:25:00 +00:00
build-pkg.lua Turns out I wasn't building the syscall libraries. Do so. 2016-08-14 11:23:57 +02:00
build-tools.lua linux386 builds. Also, forgot to turn back on the language runtimes. 2016-08-14 10:37:55 +02:00
build.mk Top, topgen, aelflod. Moved the libraries back into the platform-specific 2013-05-13 23:26:15 +01:00
descr Turns out I wasn't building the syscall libraries. Do so. 2016-08-14 11:23:57 +02:00
README Documented floating-point status. 2007-04-28 22:34:47 +00:00

# $Source$
# $State$
# $Revision$


The linux386 platform
=====================

linux386 is an i386-based BSP that produces Linux ELF executables.

This port only implements a very limited number of system calls; basically,
just enough to make the demo apps run. Adding more is easy, but there are some
subtleties that require more thought. The port should be considered only in
proof-of-concept stage right now.

Important note: you *can't* link access ELF shared libraries from these
executables. In other words, you have to all your work from inside ACK.

IEEE floating point is available, but requires an FPU.

The executables are generated with aelfslod and are extremely simple; there's
one rwx ELF section which contains all the application's code and data. This
is not optimal, but it does work.


Bugs
====

isatty() is a stub and always returns 0.


Example command line
====================

ack -mlinux386 -O -o linux386.exe examples/paranoia.c

The file linux386.exe can then be run on a i386 Linux machine (or on an
emulation thereof).


David Given
dg@cowlark.com