linux

History

Maximilian Attems 708d1f9577 * enable the juju firewire stack "implementation designed for roboustness and simplicity" disable the old firewire stack and associated options let's see if someone cries for ieee1394_eth1394 * centralize firewire settings * disable firewire on configs that disabled IEEE1394 yuhu that gets amd64 down to zero unkown config variables. :) svn path=/dists/trunk/linux-2.6/; revision=8915		2007-06-06 10:31:56 +00:00
..
Makefile.inc	debian/arch/alpha/Makefile.inc, debian/arch/amd64/Makefile.inc,	2005-09-14 21:12:04 +00:00
README.build	Merge /dists/sid/linux-2.6.	2006-05-26 12:06:07 +00:00
config	generic vfs fallback handles those cases since 04 Sep 2005	2007-05-22 14:51:21 +00:00
config.amiga	* enable the juju firewire stack	2007-06-06 10:31:56 +00:00
config.atari	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
config.bvme6000	* enable the juju firewire stack	2007-06-06 10:31:56 +00:00
config.hp	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
config.mac	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
config.mvme16x	* enable the juju firewire stack	2007-06-06 10:31:56 +00:00
config.mvme147	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
config.q40	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
config.sun3	CLEAN_COMPILE is gone from Kconfig since more than one year,	2007-05-23 11:58:05 +00:00
defines	add "type: plain" to arch/m68k/defines	2007-05-12 15:47:33 +00: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.