From: Randy Dunlap <randy.dunlap@oracle.com>
To: Marc Perkel <marc@perkel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: io_apic compile error
Date: Mon, 30 Oct 2006 21:26:29 -0800 [thread overview]
Message-ID: <20061030212629.8f9e9499.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4546D8AA.30309@perkel.com>
On Mon, 30 Oct 2006 21:01:30 -0800 Marc Perkel wrote:
>
>
> Randy Dunlap wrote:
> > On Mon, 30 Oct 2006 20:22:58 -0800 Marc Perkel wrote:
> >
> >
> >> getting a compile error when compiling 2.6.19rc3. Thought someone might want to fix this.
> >>
> >> CC arch/x86_64/kernel/io_apic.o
> >> arch/x86_64/kernel/io_apic.c: In function 'ioapic_pirq_setup':
> >> arch/x86_64/kernel/io_apic.c:412: error: 'MAX_PIRQS' undeclared (first use in this function)
> >> arch/x86_64/kernel/io_apic.c:412: error: (Each undeclared identifier is reported only once
> >> arch/x86_64/kernel/io_apic.c:412: error: for each function it appears in.)
> >> arch/x86_64/kernel/io_apic.c:417: error: 'pirq_entries' undeclared (first use in this function)
> >> arch/x86_64/kernel/io_apic.c:419: error: 'pirqs_enabled' undeclared (first use in this function)
> >> arch/x86_64/kernel/io_apic.c:412: warning: unused variable 'ints'
> >> make[1]: *** [arch/x86_64/kernel/io_apic.o] Error 1
> >> make: *** [arch/x86_64/kernel] Error 2
> >>
> >
> > Hm, it builds for me. Please post your .config file.
> >
> >
> >
> ok - here it is
>
> #
> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.19-rc3
> # Mon Oct 30 20:20:25 2006
Odd. That .config builds fine for me too.
Is this a unmodified 2.6.19-rc3? How did you get it?
Maybe someone else can discover the problem.
---
~Randy
prev parent reply other threads:[~2006-10-31 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 4:22 io_apic compile error Marc Perkel
2006-10-31 4:34 ` Randy Dunlap
2006-10-31 5:01 ` Marc Perkel
2006-10-31 5:26 ` Randy Dunlap [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=20061030212629.8f9e9499.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.