NetBSD

History

skrll b263dbdd73 Be more gcc like in the way we deal with libgcc so that sh3/hppa millicode and exception handling have a chance of working properly. - creates libgcc, libgcc_eh and libgcc_s - updates LIBGCC_SPEC to use them appropriately. There's a hack in here at the moment with respect to libgcc_so in that it is preferable to link against libgcc_so will only when -shared-libgcc is specified (the c++ frontend does this automatically.) Configurations where LINK_EH_SPEC is defined already do this. The gcc configuration for NetBSD/alpha and another NetBSD platform (I forget which) actually define LINK_EH_SPEC probably by accident rather than design. - updates share/mk to use the compiler's knowledge of what needs linking into libraries and executables. This removes an hppa hack. - updates the sets for the newly created libgcc* files. - support for linking against the _pg version of libgcc has been removed.		2004-02-15 19:52:27 +00:00
..
Makefile	Be more gcc like in the way we deal with libgcc so that sh3/hppa millicode	2004-02-15 19:52:27 +00:00
README.mknative	Fix some paths.	2004-02-13 03:01:21 +00:00
mknative-gcc	Updates so that mknative gets the right things.	2004-02-10 09:37:58 +00:00
mknative.common	…

README.mknative

$NetBSD: README.mknative,v 1.3 2004/02/13 03:01:21 simonb Exp $

This file describes how to bootstrap the native toolchain on a new NetBSD
platform (and how to update the new toolchain files, if needed).  These
files may be generated on a cross-compile host without problems.

NOTE:  DO NOT RUN "mknative" BY HAND!  It requires the Makefile in this
directory to set up certain environments first.

Since libc's features change over time, the config.h files can change as a
result; thus the instructions below are the same no matter whether
bootstrapping on a cross or native host.  This is important: even on a
"native" host, you should bootstrap the toolchain by building from an
up-to-date source tree to a $DESTDIR using the exact same instructions.

In these notes, MACHINE is the $MACHINE of the target.  These files can be
cross-generated.  Though a $MACHINE_ARCH all uses the same config files, you
must pick a specific $MACHINE so that building the requisite bits below will
work.

1. Set MKMAINTAINERTOOLS=yes in mk.conf.  (Needed so that src/tools/gettext
   gets built, eliciting proper HAVE_*GETTEXT* defns in config.h files.)

2. Build and install a cross toolchain (via "build.sh -m MACHINE tools").

3. In src/tools/gcc, do "nbmake-MACHINE bootstrap-libgcc".

   This will create just enough glue in src/gnu/lib/libgcc3/arch to make it
   possible to build, based on the toolchain built in ${.OBJDIR}/build.
   Because the files generated in this step contain things like
   -DCROSS_COMPILE, they are not suitable for committing.  Step 7 below
   will regenerate the "proper" libgcc config files.

4. At top level, do
   "nbmake-MACHINE do-distrib-dirs obj includes MKGCC=no MKBFD=no".

5. In src/gnu/lib/libgcc3, do "nbmake-MACHINE obj includes".

6. In each of src/lib/csu, src/gnu/lib/libgcc3, src/lib/libdes, and src/lib,
   do "nbmake-MACHINE all install".

   Optionally, all of the following may be set in the environment to reduce
   the amount of code needed to build at this step.  Basically, it must be
   possible for static binaries to build and base system libs to exist so
   that "configure" can do its job for the target--these MK* options omit
   the rest for this stage of the build.

   MKCRYPTO=no
   MKLINT=no
   MKPROFILE=no
   MKSHARE=no

7. In src/tools/gcc, do "nbmake-MACHINE native-gcc".

   This will do a full configury in ${.OBJDIR}/.native that is a "Canadian"
   cross toolchain (--build reflects the host platform, but --host and
   --target are the target).  The result is a tree that would build a
   native-to-NetBSD compiler on a cross host, and mknative pulls glue data
   from this.

8. Try out a full build using "nbmake-MACHINE"; the result should include
   a native compiler.

9. If all is well, commit the glue files added to src/gnu/{lib,usr.bin}/*.

- tv@NetBSD.org