Re: Compile failure: 2.4.19-rc2-ac2

[Brandon Low]

Do you have both of the APIC options selected in your config?  IF both 
IO-APIC and LOCAL-APIC are configured you shouldn't see this error, the 
problem occurs because the definition  of the dest_PRIORITY enums is 
#ifdef IO_APIC but the uses are not, perhaps the uses should use literals 
#ifndef IO_APIC, I"m not sure what the currect fix is, but doing a little 
bit of #ifdef in mpparse.c fixes it.  

--Brandon

On Thu, 07/18/02 at 20:26:41 -0500, Brandon Low wrote:
> I posted a crappity fix for this against -ac7, but I haven't seen the 
> problem in -rc2-acX, do you get the same error if you do make mrproper 
> first?
> 
> --Brandon
> 
> On Thu, 07/18/02 at 22:00:04 +0100, Alastair Stevens wrote:
> > 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                      '-=-'
> >       --
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [e-mail]
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/