Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify why even native hosts should use the same method to bootstrap a 

toolchain.
This commit is contained in:
tv 2002-02-27 17:49:19 +00:00
parent 3b5b0345cc
commit 9d3094001d
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
tools/toolchain/README.mknative
View File

@ -1,13 +1,17 @@
$NetBSD: README.mknative,v 1.1 2002/02/27 17:21:56 tv Exp $
$NetBSD: README.mknative,v 1.2 2002/02/27 17:49:19 tv 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; in fact,
the instructions below are the same no matter whether bootstrapping on a
cross or native host.
files may be generated on a cross-compile host without problems.
DO NOT RUN "mknative" BY HAND! It requires the Makefile in this directory
to set up certain environments first.
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