[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#322004: kernel-source-2.6.8: Fails to compile on a X86_64 platform



Frederik Schueler wrote:
> Hello,
> 
> On Fri, Aug 12, 2005 at 08:34:39PM +0200, Manolo Díaz wrote:
> 
>>>>>>arch/x86_64/kernel/entry.S: Assembler messages:
>>>>>>arch/x86_64/kernel/entry.S:81: Error: Macro with this name was already defined
>>>>>>arch/x86_64/kernel/entry.S:100: Error: Macro with this name was already defined
>>>>>>make[1]: *** [arch/x86_64/kernel/entry.o] Error 1
> 
> 
> I just recompiled kernel-image-2.6.8-amd64-2.6.8 (all flaovours) in a
> cleanroom sarge chroot, using kernel-source-2.6.18 2.6.8-16 from sarge,
> and it succeeded as expected.
> 
> what are the exact versions of 
> 
> binutils
> gcc
> libc6 
>

binutils       2.16.1-2
gcc-3.3        4:3.3.5-3
libc6          2.3.2.ds1-22

> which lead to your compilation failure?

> did you use a fresh extracted tarball, and wich command did you use to
> build?

Yes I used a fresh extrated tarball from kernel-source-2.6.8 (version
2.6.8-16) and the command for build it was:

make bzImage modules modules_install

> do you have a genuine pure64 installation or did you mix in packages from 
> the old experimental gcc-3.4 branch? 

I got a new machine, so I installed all packages from
http://amd64.debian.net/debian-pure64/ testing

does the /usr/bin/gcc symlink point to
> gcc-3.3 and did you use gcc-3.3 or gcc-3.4 to compile the kernel image?

/usr/bin/gcc points to /usr/bin/gcc-3.3 and it was the only cc compiler
installed on my machine. Afterwards I installed gcc-3.4 and gcc-4.0 to
make a probe, with the same resutls.

> Did you try to compile from a fresh extracted source tarball? 

>From the kernel-source-2.6.8 package

> I cannot reproduce this problem with sarge versions of the toolchain,
> thus I need more info. 
> 
I wasn't using Sarge but Etch
> 
> Best regards
> Frederik Schueler
> 

Best regadrs

Manolo Díaz



Reply to: