FFLAGS instead of COPTFLAGS in module builds?

[Marcello Maggioni]

Doug White writes:
> On Wed, 16 Mar 2005, Gary Jennejohn wrote:
> 
> > Why does the module build use CFLAGS instead of COPTFLAGS?
> >
> > I noticed it here during the module build:
> >
> > ===> linux (all)
> > cc -c -pipe -O2 -mmmx -m3dnow -msse -mfpmath=sse -fno-strict-aliasing -Werr
> or -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /u4/obj/usr/src/sys/amd64_32
> /opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -g 
> -I/u4/obj/usr/src/sys/amd64_32 -mno-align-long-strings -mpreferred-stack-boun
> dary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundan
> t-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-a
> rith -Winline -Wcast-qual -fformat-extensions -std=c99 /usr/src/sys/modules/l
> inux/../../i386/linux/linux_genassym.c
> > /usr/src/sys/modules/linux/../../i386/linux/linux_genassym.c:1: warning: SS
> E instruction set disabled, using 387 arithmetics
> > *** Error code 1
> >
> > My CFLAGS was used instead of the COPTFLAGS, as I would have expected.
> > After all, modules are part of the kernel.
> 
> How did you start this build?
> 

>cd /usr/src; make buildkernel

> What do you have CFLAGS and COPTFLAGS set to in make.conf?
> 

>CFLAGS is set to -pipe -O2 -mmmx -m3dnow -msse -mfpmath=sse

>COPTFLAGS is -pipe -O


Something similar also happend to me when I compiled my Stable kernel.

During the compilation of the ACPI module (if I remember well) the
compilations stopped because was used a gcc flag not supported during
the kernel compilation that I keep only in CFLAGS (-mfpmath=sse) . The
rest of the kernel has been compiled with COPTFLAGS, but that specific
driver has been compiled with CFLAGS.

Bye

Marcello