While compiling 2.4.17 today I got the following errors. I didn't cause
anything fatal, but it's something that needs fixing.
Ben Pharr
gcc -D__KERNEL__ -I/usr/src/linux-2.4.17-pre4/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -E -D__GENKSYMS__ sa1100fb.c
| /sbin/genksyms -k 2.4.17 >
/usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb.ver.tmp
sa1100fb.c:164: linux/cpufreq.h: No such file or directory
sa1100fb.c:166: asm/hardware.h: No such file or directory
sa1100fb.c:169: asm/mach-types.h: No such file or directory
sa1100fb.c:171: asm/arch/assabet.h: No such file or directory
mv /usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb.ver.tmp
/usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb
On Wed, 5 Dec 2001, Ben Pharr - Lists wrote:
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.17-pre4/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686 -E -D__GENKSYMS__ sa1100fb.c
> | /sbin/genksyms -k 2.4.17 >
> /usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb.ver.tmp
> sa1100fb.c:164: linux/cpufreq.h: No such file or directory
Looks like an incomplete ARM sync. But why are you trying to
build sa1100fb on x86 anyway ?
regards,
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
On Wed, Dec 05, 2001 at 11:25:23PM +0100, Dave Jones wrote:
> On Wed, 5 Dec 2001, Ben Pharr - Lists wrote:
> > gcc -D__KERNEL__ -I/usr/src/linux-2.4.17-pre4/include -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> > -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> > -march=i686 -E -D__GENKSYMS__ sa1100fb.c
> > | /sbin/genksyms -k 2.4.17 >
> > /usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb.ver.tmp
> > sa1100fb.c:164: linux/cpufreq.h: No such file or directory
>
> Looks like an incomplete ARM sync. But why are you trying to
> build sa1100fb on x86 anyway ?
The files are there. This is just one of the kbuild 2.4 disease -
unconditionally making module symbols for all files specified in
export-objs. Hopefully kbuild 2.5 fixes this.
--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html