Date: Fri, 19 Sep 2014 15:00:29 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: src.conf: CFLAGS/COPTFLAGS inconsistency Message-ID: <20140919150029.1f27e490.ohartman@zedat.fu-berlin.de>
index | next in thread | raw e-mail
[-- Attachment #1 --] man make.conf states, that COPTFLAGS is used for building/compiling the kernel (exclusively). The question arises: are kernel modules NOT kernel or are they kernel? The problem I face is that with optimization level -O3 loader.efi gets miscompiled and a UEFI laptop stops/reject booting. To avoid other interference, I defined COPTFLAGS in /etc/src.conf accordingly, but leave CFLAGS?=-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 mutual exclusive, the CFLAGS is ALWAYS incorporated when kernel stuff like modules and even the loader.efi is built! I consider this inconsitent, since loader.efi is definitely kernel related stuff as well as modules. It seems to me that it s not possible to separate cleanly CFLAGS and COPTFLAGS for userland/ports and kernel-only related compilations as described in the man page. [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140919150029.1f27e490.ohartman>