On Mon, May 14, 2007 at 06:45:47PM +0200, maximilian attems wrote: > heya, > > upload planed for wednesday to experimental. > > to make it available, also due to dynticks it sounds like the much better > candidate for the next d-i beta round. although there is no new xen > patch, kvm should already be interesting in 2.6.21. > buildserver seem not to pick up trunk. > > planed changes (please add yours): > * CONFIG_TIMER_STATS for i386
I would like to be able to build m68k images, but so far creating debs still fails for m68k. This patch allows me to get a little further in the build process, so I assume I can commit it, but I wouldn't mind if somebody who actually knows what is happening here and why this was introduced after 2.6.18 had a look on it: --- rules.real (revision 8579) +++ rules.real (working copy) @@ -422,7 +422,8 @@ install-image-i386-$(SUBARCH)-$(FLAVOUR)-plain_image: cp '$(DIR)/arch/$(KERNEL_ARCH)/boot/bzImage' $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION) -install-image-powerpc-$(SUBARCH)-$(FLAVOUR)-plain_image: +install-image-powerpc-$(SUBARCH)-$(FLAVOUR)-plain_image \ +install-image-m68k-$(SUBARCH)-$(FLAVOUR)-plain_image: install -m644 '$(DIR)/vmlinux' $(INSTALL_DIR)/vmlinux-$(REAL_VERSION) install-image-s390-$(SUBARCH)-$(FLAVOUR)-plain_image: Now the problem is here: dh_installdirs 'boot' /usr/bin/make -f debian/rules.real \ install-image-m68k-none-amiga-plain_image \ DIR='debian/build/build-m68k-none-amiga' INSTALL_DIR='/home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/boot' REAL_VERSION='2.6.21-1-amiga' make[3]: Entering directory `/home/cts/work/kernel/linux-2.6-2.6.21' install -m644 'debian/build/build-m68k-none-amiga/vmlinux' /home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/boot/vmlinux-2.6.21-1-amiga make[3]: Leaving directory `/home/cts/work/kernel/linux-2.6-2.6.21' cd debian/build/build-m68k-none-amiga; env -u ABINAME -u ARCH -u SUBARCH -u FLAVOUR -u VERSION -u LOCALVERSION -u MAKEFLAGS DISTRIBUTION_OFFICIAL_BUILD=1 [EMAIL PROTECTED] DISTRIBUTION_VERSION="2.6.21-1~experimental.1" make modules_install INSTALL_MOD_PATH=/home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga make[3]: Entering directory `/home/cts/work/kernel/linux-2.6-2.6.21/debian/build/build-m68k-none-amiga' [...] make[3]: Leaving directory `/home/cts/work/kernel/linux-2.6-2.6.21/debian/build/build-m68k-none-amiga' cp debian/build/build-m68k-none-amiga/.config /home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/boot/config-2.6.21-1-amiga cp debian/build/build-m68k-none-amiga/System.map //home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/boot/System.map-2.6.21-1-amiga rm /home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/lib/modules/2.6.21-1-amiga/{build,source,modules.*} rm: cannot remove /`/home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/lib/modules/2.6.21-1-amiga/build': No such file or directory rm: cannot remove `/home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/lib/modules/2.6.21-1-amiga/source': No such file or directory rm: cannot remove `/home/cts/work/kernel/linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/lib/modules/2.6.21-1-amiga/modules.*': No such file or directory make[2]: *** [install-image-m68k-none-amiga-plain] Error 1 The correct directory name would be: linux-2.6-2.6.21/debian/linux-image-2.6.21-1-amiga/lib/modules/2.6.21-1-amiga-m68k/ So either this directory name has to be changed, or REAL_VERSION='2.6.21-1-amiga' has to be changed. I guess it is the former, but I haven't figured out where. Again, it would be really helpful if whoever changed the code could give me a hint why it works on other arches but not on m68k. I haven't changed anything in rules or rules.real and it was working just fine in 2.6.18 for m68k. Why do we have all these exceptions for several arches, I thought this is the common source package? To me it looks as if things become less and less common with every new version, and if it continues like this, I will have to build m68k kernels outside of the common package again, simply because m68k images can not be built from there. There might be a perfectly good reason for all these changes, but I have been unable to find an explanation for it so far, where should I look? Full build log is here: http://people.debian.org/~cts/linux-m68k/linux-2.6_2.6.21-1~experimental.1_m68k.build Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]