Sorry to send this message twice, but I thought that for some reason it had not arrived at the list. Although it seems that both messages arrived with a delay of six hours. This can be due to some moderation of the list? On Thursday, 24 December 2009 09:45:54 -0300, Daniel Bareiro wrote: > > > b.2) Having booted an amd64 kernel and userland 32: > > > > > > # cp /boot/config-`uname -r` ./.config > > > > > > # make menuconfig > > > > > > # fakeroot make-kpkg clean > > > > > > # fakeroot make-kpkg --initrd --append-to-version=-dgb kernel_image \ > > > kernel_headers > > You still need to specify --cross-compile and --arch here. > And why in this case yes we must use these options if running an amd64 > kernel in userland 32 is not necessary to use ARCH=x86_64 in the > invocations of "make" when compiling of the traditional way? Well, thinking a little more about this subject, the cause by which this happens perhaps is that when make-kpkg consults the general architecture of the system, it obtains in (b.1) as in (b.2) that is i386. For that reason in both cases it is necessary to use --cross-compile and --arch. Nevertheless when being used the compilation of the traditional way, this becomes by outside any own control of Debian and the architecture that will be used by default is the one of running kernel. Is correct this asseveration? Merry Christmas. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Lenny - Linux user #188.598
Attachment:
signature.asc
Description: Digital signature