linux-kernel - Re: How can I build a 2.4 kernel on a 2.6 System

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 26 Oct 2008 11:41:04 +0100
From:	Willy Tarreau <w@....eu>
To:	Jörg Dohle <j.d.-linux-kernel@...or.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How can I build a 2.4 kernel on a 2.6 System

On Sun, Oct 26, 2008 at 11:32:17AM +0100, Jörg Dohle wrote:
> Hello Willy
> 
> Thanks for answering, but I have a problem with the compiling.
> When I try to compile the 2.4 kernel with the following commands:
> 
> # make clean && make mrproper
> then I restore the .config file
> # make oldconfig
> # make dep && make bzImage respectively make modules
> 
> 
> I get the following error message:
> 
> make[1]: Leaving directory 
> `/fileserver/99_Frei/kernel-build-tree/linux-2.4.21-57.EL'

OK, first it's an RHEL3 kernel, not a mainline one. The difference can
sometimes be important.

> gcc -D__KERNEL__ 
> -I/fileserver/99_Frei/kernel-build-tree/linux-2.4.21-57.EL/include -Wall 
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common 
>  -Wno-unused -fomit-frame-pointer -pipe -freorder-blocks  -march=i386   
>  -DKBUILD_BASENAME=main -c -o init/main.o init/main.c
> init/main.c:1: Fehler: Die ausgewählte CPU unterstützt nicht den x86-64 
> Befehlssatz
> 
> English translation (by google)
> init / main.c: 1: Error: The selected CPU does not support x86-64 
> instruction

You might get native error messages by doing "export LANG=C" before
building. I think that the problem you're encountering is simply
because by default you're trying to build for a different architecture.

You should try appending "ARCH=i386" to all your make commands :

# make oldconfig ARCH=i386
# make dep ARCH=i386 && make bzImage ARCH=i386
# make modules ARCH=i386

It should theorically work, but since this is not used very often, it is
possible that you still get minor trouble.

Regards,
Willy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/