From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.5.20 -- mpparse.c:1123: `mp_ioapic_routing' undeclared
Date: 02 Jun 2002 22:18:53 -0700 [thread overview]
Message-ID: <1023081534.1684.26.camel@turbulence.megapathdsl.net> (raw)
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=athlon
-DKBUILD_BASENAME=mpparse -c -o mpparse.o mpparse.c
mpparse.c: In function `mp_parse_prt':
mpparse.c:1120: warning: implicit declaration of function
`mp_find_ioapic'
mpparse.c:1123: `mp_ioapic_routing' undeclared (first use in this
function)
mpparse.c:1123: (Each undeclared identifier is reported only once
mpparse.c:1123: for each function it appears in.)
mpparse.c:1147: warning: implicit declaration of function
`io_apic_set_pci_routing'
make[1]: *** [mpparse.o] Error 1
make[1]: Leaving directory `/usr/src/linux/arch/i386/kernel'
I think this snippet of .config is enough. Please let
me know if you need more.
CONFIG_X86=y
CONFIG_MODULES=y
CONFIG_MK7=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
# CONFIG_X86_UP_IOAPIC is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_HAVE_DEC_LOCK=y
Linux turbulence.megapathdsl.net 2.4.7-10 #1 Thu Sep 6 16:46:36 EDT 2001
i686 unknown
Gnu C 3.0.4
Gnu make 3.79.1
binutils 2.11.90.0.8
util-linux 2.11f
mount 2.11g
modutils 2.4.14
e2fsprogs 1.26
reiserfsprogs 3.x.0j
pcmcia-cs 3.1.22
PPP 2.4.1
isdn4k-utils 3.1pre1
Linux C Library 2.2.4
Dynamic linker (ldd) 2.2.4
Procps 2.0.7
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded emu10k1 soundcore sr_mod binfmt_misc ds
yenta_socket pcmcia_core autofs 3c59x appletalk ipx ipchains ide-scsi
ide-cd cdrom reiserfs nls_iso8859-1 nls_cp437 vfat fat mousedev hid
input usb-ohci usbcore ext3 jbd raid0 aic7xxx sd_mod scsi_mod
reply other threads:[~2002-06-03 5:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1023081534.1684.26.camel@turbulence.megapathdsl.net \
--to=miles@megapathdsl.net \
--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
all inboxes | Powered by JetHome®