Re: how to compile i386 kernel on amd64 in chroot-ia32?

2006-07-07 Thread Goswin von Brederlow
Emmanuel Fleury [EMAIL PROTECTED] writes:

 mons wrote:
 Hi.
 I want to compile a kernel for my other computer. I have a ia32 chrooted
 enviroment. I tried to compile it but when I do make menuconfig i
 allways have to choose only ia64 kernels.

I highly doubt that. ia64 is not amd64 but completly different.

 What shoud I change in chroot32 enviroment to make ia32 kernels?
 Please, wrote it that so noob could understand. (I always create kernel
 making make menuconfig, dpkg-make... now I have no idea what should I
 do...)


 You should do in the following way:

 1) Save your .config (if you need it)
 2) make mrproper
 3) make ARCH=i386 menuconfig
 4) ...configure your kernel...
 5) make ARCH=i386 (I'm not sure that the 'ARCH=i386' is needed here)

 And this should build an i386 kernel.

 Regards

Just use make-kpkg.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: how to compile i386 kernel on amd64 in chroot-ia32?

2006-07-07 Thread Lennart Sorensen
On Fri, Jul 07, 2006 at 02:26:39PM +0200, Goswin von Brederlow wrote:
 Emmanuel Fleury [EMAIL PROTECTED] writes:
 
  mons wrote:
  Hi.
  I want to compile a kernel for my other computer. I have a ia32 chrooted
  enviroment. I tried to compile it but when I do make menuconfig i
  allways have to choose only ia64 kernels.
 
 I highly doubt that. ia64 is not amd64 but completly different.
 
  What shoud I change in chroot32 enviroment to make ia32 kernels?
  Please, wrote it that so noob could understand. (I always create kernel
  making make menuconfig, dpkg-make... now I have no idea what should I
  do...)
 
 
  You should do in the following way:
 
  1) Save your .config (if you need it)
  2) make mrproper
  3) make ARCH=i386 menuconfig
  4) ...configure your kernel...
  5) make ARCH=i386 (I'm not sure that the 'ARCH=i386' is needed here)
 
  And this should build an i386 kernel.
 
  Regards
 
 Just use make-kpkg.

Or just run linux32 chroot  and it will automatically think the
system is i686 rather than x86_64, and all the kernel make issues go
away.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: how to compile i386 kernel on amd64 in chroot-ia32?

2006-07-01 Thread Emmanuel Fleury
mons wrote:
 Hi.
 I want to compile a kernel for my other computer. I have a ia32 chrooted
 enviroment. I tried to compile it but when I do make menuconfig i
 allways have to choose only ia64 kernels.
 What shoud I change in chroot32 enviroment to make ia32 kernels?
 Please, wrote it that so noob could understand. (I always create kernel
 making make menuconfig, dpkg-make... now I have no idea what should I
 do...)


You should do in the following way:

1) Save your .config (if you need it)
2) make mrproper
3) make ARCH=i386 menuconfig
4) ...configure your kernel...
5) make ARCH=i386 (I'm not sure that the 'ARCH=i386' is needed here)

And this should build an i386 kernel.

Regards
-- 
Emmanuel Fleury  | Office: 211
Associate Professor, | Phone: +33 (0)5 40 00 35 24
LaBRI, Domaine Universitaire | Fax:   +33 (0)5 40 00 66 69
351, Cours de la Libération  | email: [EMAIL PROTECTED]
33405 Talence Cedex, France  | URL: http://www.labri.fr/~fleury


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



how to compile i386 kernel on amd64 in chroot-ia32?

2006-06-30 Thread mons

Hi.
I want to compile a kernel for my other computer. I have a ia32 chrooted 
enviroment. I tried to compile it but when I do make menuconfig i 
allways have to choose only ia64 kernels.

What shoud I change in chroot32 enviroment to make ia32 kernels?
Please, wrote it that so noob could understand. (I always create kernel 
making make menuconfig, dpkg-make... now I have no idea what should I do...)


--
Best regards,
mons


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]