Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Sep 2019 22:39:23 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 240717] Building kernel fails when using linker from llvm ports
Message-ID:  <bug-240717-29464-etL0Rf9I1g@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-240717-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-240717-29464@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240717

sid@bsdmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Some People         |Affects Only Me

--- Comment #2 from sid@bsdmail.com ---
Thank you.

I meant that at different times, that the compiler and linker from llvm70 a=
nd
llvm80 from ports operated the same way.

LD and LINKER_TYPE had to both be set to the same linker in make.conf for i=
t to
start compiling the kernel, but it didn't work for compiling the world. This
was after removing the ld link.

When I used devel/xtoolchain-llvm* in the past, it gave an instruction to u=
se
an X prefix in from of CC, CXX, CPP and LD to XCC, XCXX ... I believe that's
all it does. The X prefix is an override for the ports tree.

It seems that the error messages for the linker should be observed in stabl=
e,
current and the later linker versions from ports. It may not be necessary f=
or
in 12.0, except for llvm90 for consistency in future versions.

--=20
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-240717-29464-etL0Rf9I1g>