public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: linux@hazard.jcu.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.5.8 compilation fail...
Date: Mon, 22 Apr 2002 17:40:22 +0530	[thread overview]
Message-ID: <20020422174022.A19113@in.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

In article <20020422100649.GA4025@hazard.jcu.cz> Jan Marek wrote:

> --VbJkn9YxBvnuCH5J
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline

> Hallo,

> I have problems with linking of kernel 2.5.8-usagi. Compilation
> ended with:

> ld -m elf_i386 -T /usr/src/usagi/kernel/linux25/arch/i386/vmlinux.lds -e
> stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
> init/version.o init/do_mounts.o \
>         --start-group \
>         arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o
> mm/mm.o fs/fs.o ipc/ipc.o \
>         /usr/src/usagi/kernel/linux25/arch/i386/lib/lib.a
> /usr/src/usagi/kernel/linux25/lib/lib.a
> /usr/src/usagi/kernel/linux25/arch/i386/lib/lib.a \
>          drivers/base/base.o drivers/char/char.o drivers/block/block.o
> drivers/misc/misc.o drivers/net/net.o drivers/media/media.o
> drivers/char/agp/agp.o drivers/ide/idedriver.o drivers/cdrom/driver.o
> sound/sound.o drivers/pci/driver.o drivers/pnp/pnp.o
> drivers/video/video.o \
>         net/network.o \
>         --end-group \
>         -o vmlinux
> init/main.o: In function `start_kernel':
> init/main.o(.text.init+0x5db): undefined reference to
> `setup_per_cpu_areas'
> make: *** [vmlinux] Error 1

You can use the attached (text/plain) patch to fix this.

Thanks
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.

[-- Attachment #2: percpufix-2.5.8-2.patch --]
[-- Type: text/plain, Size: 974 bytes --]

diff -urN linux-2.5.8-base/init/main.c linux-2.5.8-percpufix/init/main.c
--- linux-2.5.8-base/init/main.c	Mon Apr 15 00:48:46 2002
+++ linux-2.5.8-percpufix/init/main.c	Wed Apr 17 14:10:39 2002
@@ -274,6 +274,18 @@
 
 #else
 
+/* Called by boot processor to activate the rest. */
+static void __init smp_init(void)
+{
+	/* Get other processors into their bootup holding patterns. */
+	smp_boot_cpus();
+
+	smp_threads_ready=1;
+	smp_commence();
+}
+
+#endif
+
 #ifdef __GENERIC_PER_CPU
 unsigned long __per_cpu_offset[NR_CPUS];
 
@@ -302,18 +314,6 @@
 }
 #endif /* !__GENERIC_PER_CPU */
 
-/* Called by boot processor to activate the rest. */
-static void __init smp_init(void)
-{
-	/* Get other processors into their bootup holding patterns. */
-	smp_boot_cpus();
-
-	smp_threads_ready=1;
-	smp_commence();
-}
-
-#endif
-
 /*
  * We need to finalize in a non-__init function or else race conditions
  * between the root thread and the init thread may cause start_kernel to

             reply	other threads:[~2002-04-22 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 12:10 Dipankar Sarma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 13:34 Kernel 2.5.8 compilation fail bonganilinux
2002-04-22 13:56 ` Dipankar Sarma
2002-04-22 10:06 Jan Marek

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=20020422174022.A19113@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@hazard.jcu.cz \
    /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