d37c253865
The filename of the kernel image to be installed, and the stem of the
installed name, varies between architectures, so we define several
different rules to install it for different sets of architectures.
However the basic fact that we need to install this file in /boot does
not.
We also duplicate this name information in gencontrol.py and in
debian/config/{armel,armhf,sh4}/defines (used by buildcheck.py).
To address this:
* Define [image]install-stem and [build]image-file for each architecture
* Copy these settings to make-flags in gencontrol.py
* Copy [image]install-stem to the image-stem template variable in
gencontrol.py
* Replace the per-architecture rules with a single rule using those
make-flags
The per-architecture rules for ARM and PowerPC also installed DTB
and DTS files, respectively. Include those commands in the single
rule with appropriate conditions around them.
svn path=/dists/trunk/linux/; revision=21253
|
||
|---|---|---|
| .. | ||
| README.build | ||
| config | ||
| defines | ||
README.build
HOWTO cross-build m68k linux-image Building linux-image packages takes a while, especially on the "slower arches", ie m68k. Cross-compiling is an alternative, and it works very well for m68k. You need to set up a cross-compiler. The toolchain-source package has some limitations, I prefer using cross-tools, see this page for instructions: http://people.debian.org/~cts/debian-m68k/cross-compile/ Now you only have to tell the debian build system, that you do want to build packages for m68k. It used to be sufficient to pass an option to debuild, since recently you also have to set an environment variable, like this: DEB_HOST_ARCH=m68k debuild -B -am68k If you also want to build source packages, omit the -B. If you want to build images for just one of the currently nine subarches, you can uncomment some lines in the flavours section in: debian/arch/m68k/defines The first run of debuild will give you an error message that updating the configs suceeded, the second run will build the images.