Page MenuHomeFreeBSD

Allow suppression of --no-fatal-warnings.
AbandonedPublic

Authored by jonathan on Jul 22 2016, 9:59 PM.
Tags
None
Referenced Files
F145951751: D7291.id.diff
Thu, Feb 26, 11:41 AM
Unknown Object (File)
Nov 22 2025, 12:57 PM
Unknown Object (File)
Nov 21 2025, 11:57 AM
Unknown Object (File)
Nov 21 2025, 11:57 AM
Unknown Object (File)
Nov 21 2025, 11:52 AM
Unknown Object (File)
Nov 18 2025, 7:08 PM
Unknown Object (File)
Oct 30 2025, 12:32 AM
Unknown Object (File)
Oct 15 2025, 4:16 PM
Subscribers

Details

Summary

When building with an external toolchain whose linker doesn't support the
--no-fatal-warnings flag, we need a mechanism to suppress it. This mechanism
takes the form of a new make variable, LD_NO_FATAL_WARNS. If it is not set,
it defaults to --Wl,--no-fatal-warnings as now. However, it can be defined
in src.conf, at the command line, etc., to be the empty string.

Sponsored by: DARPA, AFRL

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 4586
Build 4639: arc lint + arc unit

Event Timeline

jonathan retitled this revision from to Allow suppression of --no-fatal-warnings..
jonathan updated this object.
jonathan edited the test plan for this revision. (Show Details)
jonathan added reviewers: bapt, rwatson, bdrewery, brooks.

Of course, if we wanted to ignore the --no-fatal-warnings flag altogether, we could just do:

.if !defined(LD_FATAL_WARNINGS) || ${LD_FATAL_WARNINGS} != "no"
SOLINKOPTS+=        -Wl,---fatal-warnings
.endif

However, I wouldn't want to presume that we want to do that...

This seems to have been obviated by rS303274.