public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: alan@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.5.47-ac1 fails linking
Date: Wed, 13 Nov 2002 13:00:36 +0000	[thread overview]
Message-ID: <20021113130036.GA5488@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0211130726380.16139-101000@oddball.prodigy.com>

On Wed, Nov 13, 2002 at 07:32:04AM -0500, Bill Davidsen wrote:
 > arch/i386/kernel/built-in.o: In function `identify_cpu':
 > arch/i386/kernel/built-in.o(.init.text+0x25f4): undefined reference to `mcheck_init'
 > arch/i386/kernel/built-in.o: In function `gdt_48':
 > arch/i386/kernel/built-in.o(.data+0x15b5): undefined reference to `boot_gdt_table'

Easy one. Alan, there's some detritus left hanging around in
arch/i386/kernel/cpu/common.c 

The hunk at 319 needs to go..

Back out this bit..

diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.2.5.47/arch/i386/kernel/cpu/common.c linux.2.5.47-ac2/arch/i386/kernel/cpu/common.c
--- linux.2.5.47/arch/i386/kernel/cpu/common.c  2002-11-11 16:39:08.000000000 +0000
+++ linux.2.5.47-ac2/arch/i386/kernel/cpu/common.c  2002-11-05 15:57:59.000000000 +0000
@@ -319,6 +315,9 @@
        clear_bit(X86_FEATURE_XMM, c->x86_capability);
    }
 
+   /* Init Machine Check Exception if available. */
+   mcheck_init(c);
+
    /* If the model name is still unset, do table lookup. */
    if ( !c->x86_model_id[0] ) {
        char *p;


(Hand-pasted, so may not apply)

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2002-11-13 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 12:32 [BUG] 2.5.47-ac1 fails linking Bill Davidsen
2002-11-13 13:00 ` Dave Jones [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=20021113130036.GA5488@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=alan@redhat.com \
    --cc=davidsen@tmr.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