Skip to contentSkip to conversation

Can build 2.6.31.5 on one P4 but not another.

DISCUSSION Reg Clemens 3 participants 4 messages Nov 3, 2009

lore
Share & tools
lore
#0 lore raw

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

I dont understand how this can build on one P4 and not another.

Signature · 2 lines
                                        Reg.Clemens
                                        [email protected]
#1 lore raw
Quoted 3 lines · Reg Clemens

Can someone explain this to me.

I dont understand how this can build on one P4 and not another.

Different .configs? gcc? binutils? Those are the first 3 that come to mind...

#2 lore raw
Quoted 6 lines · Reg Clemens
Quoted 3 lines

Can someone explain this to me.

I dont understand how this can build on one P4 and not another.

Different .configs? gcc? binutils? Those are the first 3 that come to mind...

Same config files (I should have mentioned this) Different gcc's
And I would assume that the loader is the only binutil involved

Signature · 2 lines
                                        Reg.Clemens
                                        [email protected]
#3 lore raw
In reply to Reg Clemens
Quoted 10 lines · Reg Clemens

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.