From owner-freebsd-current@FreeBSD.ORG Sun May 1 22:31:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC94016A4CE for ; Sun, 1 May 2005 22:31:41 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B18043D4C for ; Sun, 1 May 2005 22:31:41 +0000 (GMT) (envelope-from hayarms@gmail.com) Received: by zproxy.gmail.com with SMTP id 34so2111082nzf for ; Sun, 01 May 2005 15:31:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hureojPMU8hRibe6NroekGJVV+ouFHb1gDFFaKTRziHOjrdCxb9dPBnSeq8m3rRWceq22O2f0MBKFq21l8EJZdCBIDNJBPlblyojcolb1qFUMj6BuTjXtRhJ7wlQzE/WpVMZcBKvjKt8XHMlYrIsxeJTbsfAhcExfbT4+4asqgA= Received: by 10.36.17.16 with SMTP id 16mr455021nzq; Sun, 01 May 2005 15:31:41 -0700 (PDT) Received: by 10.36.4.13 with HTTP; Sun, 1 May 2005 15:31:40 -0700 (PDT) Message-ID: <63f5296805050115311bccca08@mail.gmail.com> Date: Mon, 2 May 2005 00:31:41 +0200 From: Marcello Maggioni To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Mailman-Approved-At: Mon, 02 May 2005 12:01:35 +0000 Subject: Re: FFLAGS instead of COPTFLAGS in module builds? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Marcello Maggioni List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 22:31:42 -0000 Doug White writes: > On Wed, 16 Mar 2005, Gary Jennejohn wrote: >=20 > > Why does the module build use CFLAGS instead of COPTFLAGS? > > > > I noticed it here during the module build: > > > > =3D=3D=3D> linux (all) > > cc -c -pipe -O2 -mmmx -m3dnow -msse -mfpmath=3Dsse -fno-strict-aliasing= -Werr > or -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /u4/obj/usr/src/sys/amd6= 4_32 > /opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=3D80= 00 -g=20 > -I/u4/obj/usr/src/sys/amd64_32 -mno-align-long-strings -mpreferred-stack-= boun > dary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wre= dundan > t-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-a > rith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 /usr/src/sys/mod= ules/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. >=20 > How did you start this build? >=20 >cd /usr/src; make buildkernel > What do you have CFLAGS and COPTFLAGS set to in make.conf? >=20 >CFLAGS is set to -pipe -O2 -mmmx -m3dnow -msse -mfpmath=3Dsse >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=3Dsse) . The rest of the kernel has been compiled with COPTFLAGS, but that specific driver has been compiled with CFLAGS. Bye Marcello