FFLAGS instead of COPTFLAGS in module builds?

Gary Jennejohn garyj at jennejohn.org
Wed Mar 16 01:30:31 PST 2005


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 -Werror -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-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 /usr/src/sys/modules/linux/../../i386/linux/linux_genassym.c
/usr/src/sys/modules/linux/../../i386/linux/linux_genassym.c:1: warning: SSE 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.

--------
Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de



More information about the freebsd-current mailing list