mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reg Clemens <reg@dwf.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Cant build 2.6.31.5
Date: Thu, 05 Nov 2009 09:38:17 -0700	[thread overview]
Message-ID: <200911051638.nA5GcH18028889@deneb.dwf.com> (raw)

Here are more details on a problem I am having building 2.6.31.5
on a Pentium 4.

My .config file is exactly the same as it is on another Pentium 4 where
I can build with no problem, The difference is that that is Fedora11, and
the problem occurs on Fedora6.

I did a 
	make mrproper
	make -j3 bzImage ; make -j3 modules

I then did a
	make modules_install
	make install

and the install failed with the messages

[root@deneb linux-2.6.31.5-PPSv]# make install
sh /mnt/home/share/usr-src/kernels/linux-2.6.31.5-PPSv/arch/x86/boot/install.sh
 2.6.31.5-PPSv arch/x86/boot/bzImage \
                System.map "/boot"

 *** Missing file: arch/x86/boot/bzImage
 *** You need to run "make" before "make install".

make[1]: *** [install] Error 1
make: *** [install] Error 2

I reran the
	make bzImage
and got the messages

[root@deneb linux-2.6.31.5-PPSv]# make bzImage
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CALL    scripts/checksyscalls.sh
  CHK     include/linux/compile.h
  GEN     .version
  CHK     include/linux/compile.hnm semaphore.o | grep __up

  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
kernel/built-in.o:(__mcount_loc+0x838): undefined reference to 
`sleep_on_common'
kernel/built-in.o:(__mcount_loc+0x83c): undefined reference to 
`sleep_on_common'
kernel/built-in.o:(__mcount_loc+0x840): undefined reference to 
`sleep_on_common'
kernel/built-in.o:(__mcount_loc+0x844): undefined reference to 
`sleep_on_common'
kernel/built-in.o:(__mcount_loc+0x848): undefined reference to 
`sleep_on_common'
kernel/built-in.o:(__mcount_loc+0x84c): more undefined references to 
`sleep_on_common' follow
kernel/built-in.o:(__mcount_loc+0x17a8): undefined reference to `__up'
kernel/built-in.o:(__mcount_loc+0x17ac): undefined reference to `__up'
kernel/built-in.o:(__mcount_loc+0x17b0): undefined reference to `__up'
kernel/built-in.o:(__mcount_loc+0x17b4): undefined reference to `__up'
kernel/built-in.o:(__mcount_loc+0x17b8): undefined reference to `__up'
kernel/built-in.o:(__mcount_loc+0x17bc): more undefined references to `__up' 
follow
make: *** [.tmp_vmlinux1] Error 1

scanning on 
	sleep_on_common
I find it in 
	sched.c
doing a
	nm sched.o | grep sleep_on_common
I see

[reg@deneb kernel]$ nm sched.o | grep sleep_on_common
00000000 ? sleep_on_common
         U sleep_on_common

For __up, it is used in semaphore.c

doing
	nm semaphore.o | grep __up
I see
	00000000 ? __up
         U __up


I will assume that the problem is the '?' that nm is returning.
What can I do about that?
Any way to build this kernel on this OS?
I have tried copying this kernel built on another machine to this
machine, and had other problems (it just stopped during the load).

-- 
                                        Reg.Clemens
                                        reg@dwf.com



                 reply	other threads:[~2009-11-05 16:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200911051638.nA5GcH18028889@deneb.dwf.com \
    --to=reg@dwf.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®