secc
/
l4ka-pistachio
mirror of https://github.com/l4ka/pistachio.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
l4ka-pistachio/user
History
Jan Stoess 5c1b29b9c7 When building grubdisk, use strip from toolchain 2011-11-18 10:55:13 +01:00
..
Mk Silence tons of conversion warnings on newer compilers. 2011-11-18 09:40:48 +01:00
apps Add an architecture-independent tracebuffer facility (works for x86 2010-09-09 11:29:56 +02:00
contrib Added missing headers 2010-03-03 10:26:26 +01:00
include Make sigma0.h work again with plain C. Thx. to Dan Schatzberg 2011-06-02 11:33:25 -07:00
lib Introduce extended mappings, allowing to map memory addresses longer than 32 bits on 32 bit systems. For PowerPC, everything above 32 bits is mapped cache-inhibited. 2010-12-02 15:40:13 +01:00
serv Introduce extended mappings, allowing to map memory addresses longer than 32 bits on 32 bit systems. For PowerPC, everything above 32 bits is mapped cache-inhibited. 2010-12-02 15:40:13 +01:00
util When building grubdisk, use strip from toolchain 2011-11-18 10:55:13 +01:00
INSTALL Initial repository adapted to hg 2007-07-06 12:24:13 +02:00
Makefile.in Huge patchset with 2 new features: 2010-03-01 23:33:11 +01:00
README.HG Initial repository adapted to hg 2007-07-06 12:24:13 +02:00
config.mk.in - Add KERNEL to config variables 2007-11-15 14:49:49 +01:00
configure.in Modifications to allow compiling 32-bit binaries on 64-bit machines 2011-11-17 15:18:56 +01:00
install-sh Initial repository adapted to hg 2007-07-06 12:24:13 +02:00

README.HG 

Build Requirements
==================

If you obtained this version of Pistachio directly from the Mercurial
repository, you will need the following tools in order to build the
Pistachio user-level libraries and applications/servers:

   o autoheader
   o autoconf

Version 2.53 of the above mentioned tools are known to work, but older
versions of the tools might also produce correct output.  Once the
tools have been installed perform the following steps:

   1. Run `autoheader'.  This will create the file "config.h.in".

   2. Run `autoconf'.  This will create the file "configure".

You can now proceed with the remaining installation by following the
instructions given in the INSTALL file.