linux/debian/config/m68k
Ben Hutchings 516d9dac1d debian/config: Add config variable to control module signing in linux-signed
- Enable it by default
- Disable it for armel/marvell since signature verification is not enabled.
- Disable it for mips and mipsel so linux-signed can be uploaded without
  waiting for them to build
- Disable it for all architectures not in the main archive, as linux-signed
  won't support them (at least, not initially).

We don't need a variable to control signing of the image, because
we should do that for all flavours that have CONFIG_EFI_STUB=y.
2016-04-04 10:41:48 +01:00
..
README.build * debian/config: Move from debian/arch. 2007-07-24 18:31:40 +00:00
config Remove more AUFS config 2014-12-09 20:43:11 +00:00
defines debian/config: Add config variable to control module signing in linux-signed 2016-04-04 10:41:48 +01:00

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.