public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Zaplinski <o.zaplinski@mediascape.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [FIX] Compiler error on linux-2.4.11-pre4/arch/i386/kernel/mpparse.c
Date: Fri, 05 Oct 2001 18:10:00 +0200	[thread overview]
Message-ID: <3BBDDB58.850F966@mediascape.de> (raw)
In-Reply-To: <20011005172652.C3260@walker.iti.informatik.tu-darmstadt.de>

Philipp Matthias Hahn wrote:
> 
> Hello LKML!
> 
> patch-2.4.11-pre4 adds the following lines to include/acm-i386/smp.h:90
> +#ifndef clustered_apic_mode
> + #ifdef CONFIG_MULTIQUAD
> +  #define clustered_apic_mode (1)
> +  #define esr_disable (1)
> + #else /* !CONFIG_MULTIQUAD */
> +  #define clustered_apic_mode (0)
> +  #define esr_disable (0)
> + #endif /* CONFIG_MULTIQUAD */
> +#endif
> 
> which don't get included when compiling for non-SMP. Move those lines up
> before
> line 37 with "#ifdef CONFIG_SMP" and compiling should work again.

No, this does not help... :-(

gcc -D__KERNEL__ -I/usr/src/linux-2.4.11-pre4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686    -c -o io_apic.o io_apic.c
io_apic.c: In function `setup_IO_APIC_irqs':
io_apic.c:601: `INT_DELIVERY_MODE' undeclared (first use in this function)
io_apic.c:601: (Each undeclared identifier is reported only once
io_apic.c:601: for each function it appears in.)
io_apic.c: In function `setup_ExtINT_IRQ0_pin':
io_apic.c:675: `INT_DELIVERY_MODE' undeclared (first use in this function)
make[1]: *** [io_apic.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.11-pre4/arch/i386/kernel'
make: *** [_dir_arch/i386/kernel] Error 2


Olaf

  reply	other threads:[~2001-10-05 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 15:26 [FIX] Compiler error on linux-2.4.11-pre4/arch/i386/kernel/mpparse.c Philipp Matthias Hahn
2001-10-05 16:10 ` Olaf Zaplinski [this message]
2001-10-05 17:39   ` Martin J. Bligh

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=3BBDDB58.850F966@mediascape.de \
    --to=o.zaplinski@mediascape.de \
    --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