From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 13:01:09 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 413DE284 for ; Fri, 19 Sep 2014 13:01:09 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE4F9ECD for ; Fri, 19 Sep 2014 13:01:08 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1XUxoA-002Rvf-Pu>; Fri, 19 Sep 2014 15:01:06 +0200 Received: from [141.89.176.137] (helo=hermann.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1XUxoA-000lX5-Op>; Fri, 19 Sep 2014 15:01:06 +0200 Date: Fri, 19 Sep 2014 15:00:29 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: src.conf: CFLAGS/COPTFLAGS inconsistency Message-ID: <20140919150029.1f27e490.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/qF4B2v02Njo+bW=Fa1fxJwS"; protocol="application/pgp-signature" X-Originating-IP: 141.89.176.137 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2014 13:01:09 -0000 --Sig_/qF4B2v02Njo+bW=Fa1fxJwS Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable man make.conf states, that COPTFLAGS is used for building/compiling the ker= nel (exclusively). The question arises: are kernel modules NOT kernel or are th= ey kernel? The problem I face is that with optimization level -O3 loader.efi gets misc= ompiled and a UEFI laptop stops/reject booting. To avoid other interference, I defined CO= PTFLAGS in /etc/src.conf accordingly, but leave CFLAGS?=3D-O3 in /etc/make.conf for= compilation of regular ports and the rest of the OS. I can observe that with CFLAGS set, either in make.conf, or src.conf or mut= ual exclusive, the CFLAGS is ALWAYS incorporated when kernel stuff like modules and even t= he loader.efi is built! I consider this inconsitent, since loader.efi is definitely kerne= l related stuff as well as modules. It seems to me that it s not possible to separate cleanly CFLAGS and COPTFL= AGS for userland/ports and kernel-only related compilations as described in the man= page.=20 --Sig_/qF4B2v02Njo+bW=Fa1fxJwS Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUHCjyAAoJEOgBcD7A/5N8zhgH/1uOVm8pFq72agSSgfB77Oa2 IzQpCgns2wKNodP+x/VgaY3LF4RlWJwqZE3V0qlBXL7nXUzx47fxQWR+F0IYQvzG rKWV/tgJqr7kn+5KWttgvMedC5m6FyvG+nvfqEwWcId3l4gz8lmp/7GN/+vEYv4Y CNpzfX9Gd3NawGZqrrJFulqbd5wIHBjxNYe2rFLdvh5YUsd/NEO3PEx7bnrl131j uloCKems6IsQMieg6Iiy+duyhTlfzfl2ibNS4y+RStqCIbWa69GClwM2X0THFxl3 Nf0wt1SK1SI0jiJYUkkD06y7FzXDFGbjufaD9Ns5s5POGXxoDO/dDD5q22DNoQg= =T8p0 -----END PGP SIGNATURE----- --Sig_/qF4B2v02Njo+bW=Fa1fxJwS--