kern.mk: Fix wrong variable being used for linker path after 172a624f0
When I synchronized kern.mk with bsd.sys.mk, I accidentally changed
CCLDFLAGS to LDFLAGS which is not used by the kernel builds. This commit
should unbreak the GitHub actions cross-build CI. I didn't notice it
locally because cheribuild already passes -fuse-ld in the linker flags as
it predates this being done in the makefiles.
Reported By: Jose Luis Duran
Fixes: 172a624f0
("Silence annoying and incorrect non-default linker warning with GCC")
This commit is contained in:
parent
e0fd837a30
commit
01fe4cac28
@ -283,9 +283,9 @@ CFLAGS+= -std=${CSTD}
|
||||
.if ${COMPILER_TYPE} == "clang"
|
||||
# Note: Clang does not like relative paths for ld so we map ld.lld -> lld.
|
||||
.if ${COMPILER_VERSION} >= 120000
|
||||
LDFLAGS+= --ld-path=${LD:[1]:S/^ld.//1W}
|
||||
CCLDFLAGS+= --ld-path=${LD:[1]:S/^ld.//1W}
|
||||
.else
|
||||
LDFLAGS+= -fuse-ld=${LD:[1]:S/^ld.//1W}
|
||||
CCLDFLAGS+= -fuse-ld=${LD:[1]:S/^ld.//1W}
|
||||
.endif
|
||||
.else
|
||||
# GCC does not support an absolute path for -fuse-ld so we just print this
|
||||
|
Loading…
Reference in New Issue
Block a user