Version 18 (modified by 18 years ago) ( diff ) | ,
---|
Bootstrapping steps:
- Modify env.sh to accept the uname output.
- Modify header.kmk to accept and correctly configure the platform / target OS.
- Run kBuild/env.sh to configure the kBuild environment.
- Copy unix like tools from you system to kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/. kBuild requires all ash (bash is recommended), cat, cp, echo, install, ln, mkdir, mv, rm, rmdir and (gnu) sed. The kBuild copies must be prefixed with
kmk_
. These tools will be replaced later in the bootstrapping. - Configure and build GNU sed:
- Go to the src/sed directory.
- Run aclocal, autoconf and automake in src/sed if needed.
- Create and enter src/sed/obj.
- Run ../configure --disable-nls.
- Run make
- Copy config.h to src/sed/config.h.$BUILD_TARGET (or similar, see Makefile.kmk).
- Copy sed/sed[.exe] to kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/kmk_sed[.exe].
- Configure and build plain GNU Make:
- Run aclocal, autoconf and automake in src/gmake if needed.
- Create and enter src/gmake/obj.
- Run ../configure --disable-nls.
- Run make
- Copy config.h to src/gmake/config.h.$BUILD_TARGET (or similar, see Makefile.kmk). Append empty string #defines for LOCALEDIR, LIBDIR, INCLUDEDIR and ALIASPATH (see config.h.linux).
- We've now got our own make binary which will be used further down.
- Build src/gmake using the GNU Make we just made:
- Go to the src/gmake directory.
- obj/make -f Makefile.kmk
- When it breaks fix the compiler / linker error and redo the previous step.
- Copy out/$BUILD_TARGET.$BUILD_TARGET_ARCH/release/kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/ to kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/.
- Rebuild everything using kmk (which should now be in the path):
- Run kBuild/env.sh (or continue in the shell from the previous step).
- Go to the root.
- kmk BUILD_TYPE=release rebuild
- Fix build breaks and repeat the previous step.
- Copy out/$BUILD_TARGET.$BUILD_TARGET_ARCH/release/kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/ to kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/.
- Add and commit the changes (including the binaries).
Note! On GNU/Linux make sure you have a real yacc install. GNU bison is not sufficiently compatible with yacc to make src/ash (from NetBSD) happy.
New Bootstrapping Steps (src/gmakenew)
- Modify env.sh to accept the uname output. A kBuild BUILD_TARGET / BUILD_PLATFORM OS name must be decided upon at this point. If the architecture and/or processor is new to kBuild, new (unique) names need to be found here as well.
- Modify header.kmk to accept and correctly configure the platform / target OS.
- Run kBuild/env.sh to configure the kBuild environment.
- Port and bootstrap kmk.
The bootstrap kmk build is made using the GNU automake/autoconf setup of GNU make. Which means that the initial port of the kmk code has to be done in that environment. Since porting isn't a common day thing, nor is bootstrapping this is just something we have to live with.
- The source is derived from the GNU make CVS and not a GNU make tarball. This means all the auto-stuff has to be created first. Run this from the src/gmake directory:
autoreconf -i
For solving problems check out the autoreconf manual page and README.cvs. - Create a subdirectory
obj
for to do the build within. This avoids confusion later and simplifies cleanup. Enter the directory. - Run configure:
../configure
- Build it:
make
Don't expect it to build on the first try on a new platform. Fix build errors and repeat until success or you give up in frustration... - Copy (or symlink) the resulting
kmk
tokBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/
. You may have to create this directory first. - The kmk bootstrapping is now done (unless of course, bugs in the port needs addressing).
- The source is derived from the GNU make CVS and not a GNU make tarball. This means all the auto-stuff has to be created first. Run this from the src/gmake directory:
- Copy or symlink a bournshell compatible shell (ash is preferred) to
kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/kmk_ash
./bin/sh
or/bin/bash
is usually a good choice.
- Configure/Port and build the kmk, ash, sed, and kDep* (all found in source) using the bootstrap kmk. It's recommended to take one directory at a time and start with kmk since that's almost done now. The job that's required for each directory is roughly this:
- Check if anything special is required in Makefile.kmk for your OS.
- If it's a autoconf based tool run configure to (re)generate the config.h for your OS.
These are usually cached as
config.h.$(BUILD_TARGET)
files. Note. You might wish to check if it builds and checks out cleanly in the autoconf/automake framework. Applies to sed and kmk/gmake. - Try build:
kmk
Address build errors (and warnings) until it builds successfully. - If it's a autoconf/automake based tool and it got a testharness/suite, it is recommended to test the binary you've just built in it. Applies to sed and to some degree kmk/gmake.
- Copy the resulting binary/binaries to
kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/
. - Move on to the next tool.
- When everything builds and you've copied the new binaries to the kBuild/bin/x.y location, it's time to rebuild everything using the new binaries.
- Remove the
out/
directory found in the root of the kBuild tree. - Run
kmk
from the root. - Replace binaries in
kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/
with the new ones fromout/$BUILD_TARGET.$BUILD_TARGET_ARCH/$BUILD_TYPE/kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/
. - It doesn't hurt to repeat this sequence once more.
- Remove the
- Create patches and submit to bird along with a release build of the tools binaries.
Trouble Shooting
- On Solaris cp doesn't like being called kmk_cp. So, when building src/gmake for the first time, it might be necessary to add
CP=/bin/cp
to the make command line. - The sed and GNU make configure scripts might not like the system sed. Try find a GNU sed binary or bootstrap it yourself. Copy you sed program to kBuild/bin/$BUILD_TARGET.$BUILD_TARGET_ARCH/ (without any prefix) and it'll be used instead of the system sed.
- Use a real YACC when compiling ash. GNU bison will not work (yyerrstatus undeclared error). You can add YACC=/path/to/real/yacc to the kmk command line if it's not in the PATH.
Note:
See TracWiki
for help on using the wiki.