1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
Building cross-compiler Debian packages
---------------------------------------
It is possible to build C and C++ cross compilers and support libraries
from gcc-3.3 source package. This document describes how to do so.
Cross-compiler build support is not perfect yet, please send fixes
and improvements to debian-gcc@lists.debian.org
Before you start, you should probably check available pre-built
cross-toolchain debs. At the time of writing (Jul 2004) those are
available from
http://zigzag.lvk.cs.msu.su/~nikita/debian/
If they are no longer there, you may check EmDebian web site at
http://emdebian.sf.net/
or ask debian-embedded@lists.debian.org for newer location.
0. What's wrong with toolchain-source approach
Package toolchain-source contains sources for binutils and gcc, as well as
some support scripts to build cross-compiler packages. They seem to work.
However, there is one fundamental problem with this approach.
Gcc package is actively maintained and frequently updated. These updates
do contain bug fixes and improvements, especially for non-x86 architectures.
Cross-compilers built using toolchain-source will not get those fixes unless
toolchain-source package is updated after each binutils and gcc update.
The later is not hapenning in real life. For example, toolchain-source
was upgraded from gcc-3.2 to gcc-3.3 half a year later than gcc-3.3 became
Debian default compiler.
Keeping toolchain-source package up-to-date requires lots of work, and seems
to be a waste of time. It is much better to build cross-compilers directly
from gcc source package.
1. What is needed to build a cross-compiler from gcc-3.3 source
1.1. dpkg-cross package
Dpkg-cross package contains several tools to manage cross-compile environment.
It can convert native debian library and lib-dev packages for the target
architecture to binary-all packages that keep libraries and headers under
/usr/$(TARGET)/.
Also it contains helper tools for cross-compiling debian packages. Some of
these tools are used while building libgcc1 and libstdc++ library packages.
The resulting library packages follow the same convensions as library packages
converted by dpkg-cross.
Currently, at least version 1.18 of dpkg-cross is needed for cross-gcc
package build.
1.2. cross-binutils for the target
You need cross-binutils for your target to build cross-compiler.
Binutils-multiarch package will not work because it does not provide cross-
assemblers.
If you don't want to use pre-built cross-binutils packages, you may build
your own from binutils debian source package, using patches posted to
bug #231707. Please use the latest of patch versions available there.
Alternatively, you may use toolchain-source package to build cross-binutils
(but in this case you will probably also want to use toolchain-source
to build cross-compiler itself). However, multilib'ed cross-compilers may
not build or work with these binutils.
1.3. libc for target
You also need libc library and development packages for the target
architecture installed.
To get those, download linux-kernel-headers, libdb1-compat, libc6,
and libc6-dev binary debs for your target, convert those using
dpkg-cross -b, and install resulting -arch-cross debs. Consult dpkg-cross
manual page for more information.
Building with/for alternative libc's is not supported yet (but this is in
TODO).
Note that if you plan to use your cross-toolchain to develop kernel drivers
or similar low-level things, you will probably also need kernel headers
for the exact kernel version that your target hardware uses.
2. Building cross-compiler packages
Get gcc-3.3 source package.
Unpack it using dpkg-source -x, and cd to the package directory.
Set GCC_TARGET environment variable to the target architectire name. Note
that currently you should use debian architecture name (i.e 'powerpc' or 'arm'),
not GNU system type (i.e. 'powerpc-linux' or 'arm-linux'). Setting GCC_TARGET
to GNU system type will cause cross-compiler build to fail.
Instead of setting GCC_TARGET, target architecture name may be put into
debian/target file. If both GCC_TARGET is defined and debian/target file
exists, GCC_TARGET is used.
Run debian/rules control. This will change debian/control file, adjusting
build-depends.
Build the package using dpkg-buildpackage.
3. Using crosshurd
Jeff Bailey <jbailey@raspberryginger.com> suggests alternate way to setup
environment to build cross-compiler, using 'crosshurd' package.
Crosshurd is like debootstrap but cross-arch, and works on the Hurd,
Linux and FreeBSD. (The name is historical).
If you setup your environment with crosshurd, you will need to fix symlinks
in lib and usr/lib to be relative instead of absolute. For example:
lrwxrwxrwx 1 root root 20 2004-05-06 23:02 libcom_err.so -> /lib/libcom_err.so.2
Needs to be changed to:
lrwxrwxrwx 1 root root 20 2004-05-06 23:02 libcom_err.so -> ../../lib/libcom_err.so.2
Also, if you choose this method, set the environment variable 'with_sysroot'
to point to the ABSOLUTE PATH where the crosshurd was done.
Note however that build-depends of cross-gcc and dependencies in generated
libgcc1 and libstdc++ packages assume that you use dpkg-cross to set up
your environment, and may be wrong or incomplete if you use alternate methods.
But probably you don't care.
--
Nikita V. Youshchenko <yoush@cs.msu.su>
|
