From: Alastair Stevens <alastair@camlinux.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Compile failure: 2.4.19-rc2-ac2
Date: 18 Jul 2002 22:00:04 +0100 [thread overview]
Message-ID: <1027026004.13704.6.camel@dolphin.entropy.net> (raw)
Hi Alan & others
Just a compile failure report for 2.4.19-rc2-ac2, hope it's useful. My
system is an ordinary Athlon XP running RH7.3, and I'm currently on
2.4.19-pre10-ac2. Using the same .config which I've been using for quite
some time, I got the following error, having done "make oldconfig dep
clean modules bzImage" from a pristine tree:
gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
-DKBUILD_BASENAME=pci_irq -c -o pci-irq.o pci-irq.c
gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
-DKBUILD_BASENAME=mtrr -DEXPORT_SYMTAB -c mtrr.c
gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
-DKBUILD_BASENAME=msr -DEXPORT_SYMTAB -c msr.c
gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
-DKBUILD_BASENAME=cpuid -DEXPORT_SYMTAB -c cpuid.c
gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
-DKBUILD_BASENAME=mpparse -c -o mpparse.o mpparse.c
mpparse.c:74: `dest_LowestPrio' undeclared here (not in a function)
mpparse.c: In function `smp_read_mpc':
mpparse.c:609: `dest_Fixed' undeclared (first use in this function)
mpparse.c:609: (Each undeclared identifier is reported only once
mpparse.c:609: for each function it appears in.)
mpparse.c:609: `dest_LowestPrio' undeclared (first use in this function)
make[1]: *** [mpparse.o] Error 1
make[1]: Leaving directory `/home/alastair/linux-2.4/arch/i386/kernel'
make: *** [_dir_arch/i386/kernel] Error 2
Regards
Alastair
--
\\ Alastair Stevens Cambridge
\\ Technical Director / \..-^..^...
\\ |Linux solutions \
\\ 01223 813774 \ /........../
\\ www.camlinux.co.uk '-=-'
--
next reply other threads:[~2002-07-18 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 21:00 Alastair Stevens [this message]
2002-07-19 1:26 ` Compile failure: 2.4.19-rc2-ac2 Brandon Low
2002-07-21 0:44 ` Brandon Low
2002-08-01 21:21 ` 2.4.19-rc5: boot failure with IO-APIC built in Alastair Stevens
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 13:47 Compile failure: 2.4.19-rc2-ac2 Alastair Stevens
2002-07-20 21:04 ` Alan Cox
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=1027026004.13704.6.camel@dolphin.entropy.net \
--to=alastair@camlinux.co.uk \
--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