mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: khromy@lnuxlab.ath.cx (khromy)
To: linux-kernel@vger.kernel.org
Cc: miles@megapathdsl.net, lostlogic@gentoo.org
Subject: Re: Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c (possible fix)
Date: Tue, 16 Jul 2002 03:54:37 -0400	[thread overview]
Message-ID: <20020716075437.GA9226@lnuxlab.ath.cx> (raw)
In-Reply-To: <1026792066.1417.19.camel@localhost.localdomain>

On Mon, Jul 15, 2002 at 09:01:06PM -0700, Miles Lane wrote:
<snip>
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -I /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/include -DKBUILD_BASENAME=mpparse  -c -o mpparse.o mpparse.c
> In file included from mpparse.c:25:
> /usr/src/linux/include/asm/smp.h:45:1: warning: "INT_DELIVERY_MODE" redefined
> /usr/src/linux/include/asm/smp.h:42:1: warning: this is the location of the previous definition
> mpparse.c:72: parse error before numeric constant
> mpparse.c:76: parse error before numeric constant
> mpparse.c:77: parse error before numeric constant
> mpparse.c:78: parse error before numeric constant
> mpparse.c:79: parse error before numeric constant
> mpparse.c: In function `smp_read_mpc':
> mpparse.c:601: invalid lvalue in assignment
<snip>

I don't know how correct the following patch might be, but it allows
mpparse.c to compile.

(diff against 2.4.19-rc1-ac5)

--- include/asm-i386/smp.h.old	Tue Jul 16 03:21:52 2002
+++ include/asm-i386/smp.h	Tue Jul 16 03:39:00 2002
@@ -34,11 +34,6 @@
 #define		INT_DEST_ADDR_MODE		1     /* logical delivery */
 # endif
 #else
-#define		clustered_apic_mode		(0)
-#define		clustered_apic_logical		(0)
-#define		clustered_apic_physical		(0)
-#define		apic_broadcast_id		(APIC_BROADCAST_ID_APIC)
-#define		esr_disable			(0)
 #define		INT_DELIVERY_MODE		1     /* logical delivery */
 #define		TARGET_CPUS			0x01
 #define		INT_DEST_ADDR_MODE		1     /* logical delivery */

-- 
L1:	khromy		;khromy(at)lnuxlab.ath.cx

  parent reply	other threads:[~2002-07-16  7:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 21:48 Linux 2.4.19-rc1-ac5 Alan Cox
2002-07-15 22:10 ` Rudmer van Dijk
2002-07-15 23:14   ` H. Peter Anvin
2002-07-15 23:25     ` Robert Love
2002-07-16  0:28     ` Alan Cox
2002-07-15 23:21       ` H. Peter Anvin
2002-07-15 23:29         ` Robert Love
2002-07-15 23:47           ` H. Peter Anvin
2002-07-16  6:46             ` Rudmer van Dijk
2002-07-16  4:01 ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c Miles Lane
2002-07-16  4:14   ` Brandon Low
2002-07-16  7:54   ` khromy [this message]
2002-07-16  8:07     ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c (possible fix) khromy
2002-07-16 10:09     ` Alan Cox
2002-07-16 11:45 ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-16 17:07   ` Andre Hedrick
2002-07-16 17:13     ` Alan Cox
2002-07-19 20:36       ` Linux 2.4.19-rc2-ac2 Ian Soboroff
2002-07-19 21:02         ` Philippe Gramoullé
2002-07-22 13:03           ` mbs
2002-07-17 17:11   ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-28 23:06     ` Kasper Dupont
2002-07-29 12:00       ` Alan Cox
2002-07-29 13:58         ` Kasper Dupont

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=20020716075437.GA9226@lnuxlab.ath.cx \
    --to=khromy@lnuxlab.ath.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lostlogic@gentoo.org \
    --cc=miles@megapathdsl.net \
    /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

Powered by JetHome