mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Midian <midian@ihme.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Compile failure 2.4.22-pre3-ac1
Date: 09 Jul 2003 12:10:56 -0600	[thread overview]
Message-ID: <1057774256.8754.46.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1057772247.3757.9.camel@midux>

On Wed, 2003-07-09 at 11:37, Midian wrote:
> Hello Alan,
> I've tryed to compile 2.4.22-pre3-ac1, but every time I get this error:
> 
> arch/i386/kernel/kernel.o(.text.init+0x7803): In function
> `setup_ioapic_ids_from_mpc':
> : undefined reference to `xapic_support'
> arch/i386/kernel/kernel.o(.text.init+0x7a16): In function
> `setup_ioapic_ids_from_mpc':
> : undefined reference to `xapic_support'
> make: *** [vmlinux] Error 1
> 
> I've tryed to search for patches from the mailing list with no luck, is
> there some patches for this?
> 
> Regards

I posted this workaround here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105760102522650&w=2

but as Adrian Bunk pointed out in a response, the problem is that
"changes to arch/i386/kernel/mpparse.c got lost at the update of -ac to -pre3".

If you want to be slightly more adventurous than using my
workaround patch, you could copy the mpparse.c file from 2.4.21-ac4.
That was compile tested but not run tested.

Steven


      reply	other threads:[~2003-07-09 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 10:49 [PATCH] Readd BUG for SMP TLB IPI Andi Kleen
2003-07-09 11:27 ` Alan Cox
2003-07-09 11:41   ` Andi Kleen
2003-07-09 16:53     ` Alan Cox
2003-07-09 16:58       ` Andi Kleen
2003-07-09 17:04         ` Alan Cox
2003-07-09 17:32           ` Andi Kleen
2003-07-09 23:38             ` Alan Cox
2003-07-09 17:37           ` Compile failure 2.4.22-pre3-ac1 Midian
2003-07-09 18:10             ` Steven Cole [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=1057774256.8754.46.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midian@ihme.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®