用cygwin交叉编译环境构造基于newlib的目标系统 收藏
%%howto-version: 1.0
%%title: Building Cygwin hosted newlib-based target toolchain
%%url:
%%category: cygwin
%%filename: cygwin-to-newlib-cross-howto
%%author: Mumit Khan
This howto provides a roadmap to building a newlib-based target
development toolchain such as powerpc-eabi hosted on Cygwin
(ix86-pc-cygwin) platform. Even though I am using Cygwin as the host
in this HOWTO, the information here is just as applicable to other hosts.
TOC:
- Background
- Preliminaries
- Build steps
- Postscript
Created: Thu Jan 25 11:10:11 CST 2001
Last Modified: Thu Jan 25 15:05:13 CST 2001
Background:
===========
When it comes to cross-compiling (the simple kind or the canadian kind),
three terms are very important -- host, target and build. The host is
the machine that the resulting toolchain will run on, the build is the
machine that the resulting toolchain are being built on, and target is
the machine that resulting toolchain will create binaries for. The most
usual case is where host == build == target (eg., if you're using a Linux
compiler on a Linux box that was created on a Linux box); in the case of
most cross-compilers, host == build, target is different (eg., host and
build could be say Linux and target could be say i686-pc-cygwin, so that
when you compile/link on Linux box using this toolchain, you create
binaries that will run on i686-pc-cygwin); in the case of building a
canadian cross compiler, host, build and target may all be different
(I'll refrain from expounding on this one, and leave it to your
imagination).
Ok, so let's say we have a PC running Win2k and Cygwin, and we want to
able to build powerpc-eabi binaries on that PC. The runtime library
for that target is newlib, which should be quite known to those who
are into this sort of thing. This HOWTO is applicable to all supported
GCC targets that use newlib as the runtime library, and I just happen
to be using powerpc-eabi as an example.
CrossGCC folks use various schemes, and I personally find those too
complicated, but do it my way mostly because I'm too lazy to read the
instructions.
Here're the basic steps: (Preliminaries) Decide on where you want to
install and so on, (1) Gather all the source packages you need, move
these over to the Cygwin host, (2) Build and install Binutils, (3) Build
and install *just* the C compiler in GCC, then (4) use the C compiler
just installed to build and install newlib, and finally (5) go back
and build the rest of the compilers and language support runtimes in
GCC and install those as well. Postscript shows a simple example,
and shows how to avoid GCC from always adding .exe to the executable
name (if you want to avoid that, read that before step 3).
There is one thing to note here -- you will run into the term "single
tree" build, which means that all the required components are in one
tree, and set up so that you can simply do a `configure', followed by
a `make', and you're good to go without having to go through the steps
I have outlined here. However, unless you already have a tested and
verified single-tree configuration such as GNUPro formerly from Cygnus
Solutions and now from RedHat if you are a customer, you are much better
off building each piece individually. One might think that building a
single tree out of all the individual pieces is trivial -- just unpack
on top of each other, and then combine all the common pieces. Try that
with different versions of bfd included in binutils and in gdb, and
you'll soon run into a disaster. Stick with multiple separate packages,
and you will not regret the extra keystrokes. It is after all scriptable,
so keystrokes go down to just a few.
For the purposes of this HOWTO, I've used the following packages:
1. Cygwin -- 1.1.7 (with all updates applied to date)
2. GCC -- 2.95.2-6 (part of Cygwin source distribution)
3. Binutils -- 2.10.1 (standard GNU distribution)
4. newlib -- 1.9.0 ()
Preliminaries:
==============
Scattered throughout this article are user commands that you'll type
in, and I've used ``cygwin$'' as the shell prompt.
Let's say we'll be using the following (I'm using bash, so if you're
using a csh/tcsh type shell, do the right thing):
cygwin$ host=i686-pc-cygwin
cygwin$ build=i686-pc-cygwin
cygwin$ target=powerpc-eabi
cygwin$ prefix=/usr/local/powerpc
cygwin$ src_root=/usr/local/src/gnu
Feel free to change $prefix and/or $src_root to match your environment,
but please don't mess with $host, $build and $target. Do make sure that
$src_root directory does exist. You don't have to set these shell
variables of course, but it saves me some typing and saves you from my
inevitable typos.
You should also add $prefix/bin to your PATH, but you can wait till you
have installed binutils for that (ie., end of Step 2).
Step 1:
=======
Gather all the source packages you need. The minimal set is the compiler
sources, binary utilities.
Let's say we get the following from a GNU or RedHat sourceware mirror:
gcc-2.95.2.tar.gz
binutils-2.10.1.tar.gz
newlib-1.9.0.tar.gz
Since we're building on a Cygwin host, the safe bet is to get a version
of gcc-2.95.2 from the Cygwin distribution instead which may have some
Cygwin specific fixes, which is what I use. See Cygwin home page at
to see how to download the GCC source
package using the network "setup" utility (or just ftp it over from one
the mirrors). At the time of this writing, the latest one is gcc-2.95.2-6.
Download these on your Cygwin box and unpack:
cygwin$ cd $src_root
cygwin$ tar zxf /tmp/gcc-2.95.2.tar.gz
cygwin$ tar zxf /tmp/binutils-2.10.1.tar.gz
cygwin$ tar zxf /tmp/newlib-1.9.0.tar.gz
Step 2:
=======
Build and install binutils. Never build in the source tree, so I'll just
arbitrarily pick $src_root/BUILD as the top build directory, under which
I'll build both binutils and gcc.
cygwin$ mkdir -p $src_root/BUILD/binutils
cygwin$ cd $src_root/BUILD/binutils
cygwin$ $src_root/binutils-2.10.1/configure \
--with-included-gettext \
--target=$target --host=$host --build=$build \
--prefix=$prefix -v
cygwin$ make > make.log 2>&1
If all goes well, install.
cygwin$ make install > install.log 2>&1
*IMPORTANT* Add $prefix/bin to your PATH Before going forward.
cygwin$ export PATH=$PATH:$prefix/bin
Check:
cygwin$ $target-ld --version
GNU ld 2.10.1
Copyright 2000 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
Supported emulations:
elf32ppc
Done.
Step 3:
=======
Build and install *just the C compiler* from GCC.
cygwin$ mkdir -p $src_root/BUILD/gcc
cygwin$ cd $src_root/BUILD/gcc
cygwin$ $src_root/gcc-2.95.2/configure \
--enable-languages=c,c++ \
--with-included-gettext --enable-shared --enable-threads \
--target=$target --host=$host --build=$build \
--with-newlib \
--prefix=$prefix -v
Feel free to change the arguments to --enable-languages, or leave it
out altogether if you want to build all available languages. Also,
do as you wish with --enable-shared and --enable-threads parameters.
Don't mess with the rest. The --with-newlib is critical since it
tells the compiler not to try to include stdlib.h and unistd.h when
building libgcc.a, which is built as part of the core C compiler
build (short answer: the configure script defines the inhibit_libc
macro, which in turn guards against certain target includes in
gcc/libgcc2.c file).
Now, please note that we're specifically only building the C compiler
and just that.
cygwin$ make LANGUAGES=c all-gcc > make.log 2>&1
cygwin$ mv make.log make-c-only.log
If all goes well, install.
cygwin$ make LANGUAGES=c install-gcc > install.log 2>&1
cygwin$ mv install.log install-c-only.log
Now you can build C code with the installed compiler. You could have
also built the C++ compiler as well, but since we don't need that for
building newlib, let's hold on till we're done with step 4.
Step 4:
=======
Build and install newlib:
cygwin$ mkdir -p $src_root/BUILD/newlib
cygwin$ cd $src_root/BUILD/newlib
cygwin$ $src_root/newlib-1.9.0/configure \
--target=$target --host=$host --build=$build \
--prefix=$prefix -v
cygwin$ make > make.log 2>&1
If all goes well, install.
cygwin$ make install > install.log 2>&1
Now you have the target environment in place, and you can build the
rest of the world.
Step 5:
=======
Build and install the rest of the GCC compilers and language runtime
and/or support libraries.
cygwin$ cd $src_root/BUILD/gcc
cygwin$ make > make.log 2>&1
cygwin$ make install > install.log 2>&1
Postscript:
===========
Now that you're run, you should be able to create $target target
binaries. If all goes well:
$ cat > hello.c
#include
int
main()
{
printf("hello world\n");
return 0;
}
^D
$ $target-gcc -o hello hello.c
$ ls -l hello*
hello.c hello.exe
[ btw, since our example target is powerpc-eabi, you may have to supply
at least one -m parameter, such as -msim, for this to work ]
Huh, why the .exe extension? Well, it has to do with gcc hosted on
Cygwin, and you can always patch gcc sources to get rid of the automatic
.exe addition. Just comment out the EXECUTABLE_SUFFIX macro in
$src_root/gcc-2.95.2-6/gcc/config/i386/xm-cygwin.h and rebuild gcc.
Incidentally, the whole business of first building and installing only
the C compiler part in GCC is only needed if you don't have the target
environment, newlib in this case, fully installed. After the first time,
all that is unnecessary of course.
If you're building gdb-5.0 as well (which includes the ppc simulator
by the way), you may need to comment out the declaration for strsignal
in gdb-5.0/gdb/defs.h to get it to build. Otherwise, the declaration
will not match the one in newlib (newlib's one returns a const char *,
whereas gdb's declaration omits the const).
THE END
=======
For more information on GNU Compiler Collection (GCC), see GCC home
page:
For more information on Cygwin, see Cygnus's cygwin project page:
For more information on Crossgcc, see:
For more information on binutils, see:
Latest version of this documentation, and other information related to
GNU tools on various types of windows32 system, is available from my
gnu-win32 page:
Created: Thu Jan 25 11:10:11 CST 2001
Last Modified: Thu Jan 25 15:05:13 CST 2001
Mumit Khan <>
Good luck.
%%end-howto
这位老兄真是大牛。按照他的资料和文档，是有可能做出CYGWIN的。
但这份文档对通用的制作过程说明得不够详细，应该参看他的网页和
文档后面的网站里的文档。制作WINDOWS版本肯定比LINUX的难度要
大很多，要有心理准备。
还有，把文档中的newlib改成glibc就是基于glibc的系统了。以后
是采用newlib还是glibc，恐怕还会有一番争论。
