public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Reg Clemens <reg@dwf.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can build 2.6.31.5 on one P4 but not another.
Date: Tue, 3 Nov 2009 20:22:58 +0100	[thread overview]
Message-ID: <200911032022.59466.elendil@planet.nl> (raw)
In-Reply-To: <200911031815.nA3IFCe6017661@deneb.dwf.com>

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.

      parent reply	other threads:[~2009-11-03 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 18:15 Can build 2.6.31.5 on one P4 but not another Reg Clemens
2009-11-03 18:45 ` Valdis.Kletnieks
2009-11-03 19:20   ` Reg Clemens
2009-11-03 19:22 ` Frans Pop [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911032022.59466.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reg@dwf.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox