Date: Fri, 19 Sep 2014 12:59:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193768] New: src.conf/make.conf: CFLAGS/COPTFLAGS inconsistency Message-ID: <bug-193768-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193768 Bug ID: 193768 Summary: src.conf/make.conf: CFLAGS/COPTFLAGS inconsistency Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ohartman@zedat.fu-berlin.de 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. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193768-8>