linux-kernel - Re: Can build 2.6.31.5 on one P4 but not another.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200911032022.59466.elendil@planet.nl>
Date:	Tue, 3 Nov 2009 20:22:58 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Reg Clemens <reg@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Can build 2.6.31.5 on one P4 but not another.

Reg Clemens wrote:
> Can someone explain this to me.
> I can build 2.6.31.5 on one of my Pentium 4's with no problems,
> it boots and runs.
> 
> On a second P4, the build fails (compile works, load fails) with
> comments about undefined references to:
> sleep_on_common
> and  __up
>
> These appear in sched.c and  semaphore.c.

Are you using identical configs for both machines or not?

Are you sure both machines really have the same kernel source?

Have you tried if a 'make mrproper' makes a difference (normally it should 
not)?

Do both machines have the same build environment (gcc version, binutils, 
etc)?

If you need additional help, please post the exact error messages and the 
kernel config for the failing machine.

Cheers,
FJP

P.S. Why are you building the kernels on two machines instead of doing the 
builds on one machine and then copying and installing a build for the 
second? That could save a lot of build time, even if you don't use 
identical configs.
--
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/