Date: Tue, 9 Jan 2024 08:18:46 -0500 From: mike tancsa <mike@sentex.net> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: clang 17 and ports fallout Message-ID: <04837a47-a39c-40c5-a045-2d27fb3893ac@sentex.net> In-Reply-To: <D365EB02-14AC-4F85-B687-962C20A7BA04@FreeBSD.org> References: <06381879-c328-4051-bb2f-9c3620d90fa0@sentex.net> <4a0db68d-bb13-4238-a251-74d02ff14a17@sentex.net> <D365EB02-14AC-4F85-B687-962C20A7BA04@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------93SDc0twK8siL5B3tOvjiI6a Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 1/8/2024 5:50 PM, Dimitry Andric wrote: > I fixed a lot of ports in the run-up to merging llvm-17 in 15-CURRENT, > but I could not get them all. > > The preferred way is fixing the port by removing the undefined symbols > from the linker version script in the port, but if that is not possible > or difficult, add -Wl,--undefined-version to the linker flags suppresses > the error. E.g. in the port Makefile: > > LDFLAGS+= -Wl,--undefined-version > > For an example, see: > > https://github.com/freebsd/freebsd-ports/commit/37790b26cbda11cd4bb6f237b86cd94739c4059c Thanks very much! That did indeed fix databases/rrdtool and and sysutils/flashrom builds. What is the best way to flag any such issues ? Just open a PR for each individual port ? ---Mike --------------93SDc0twK8siL5B3tOvjiI6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 1/8/2024 5:50 PM, Dimitry Andric wrote:<br> </div> <blockquote type="cite" cite="mid:D365EB02-14AC-4F85-B687-962C20A7BA04@FreeBSD.org"><span style="white-space: pre-wrap"> </span> <pre class="moz-quote-pre" wrap="">I fixed a lot of ports in the run-up to merging llvm-17 in 15-CURRENT, but I could not get them all. The preferred way is fixing the port by removing the undefined symbols from the linker version script in the port, but if that is not possible or difficult, add -Wl,--undefined-version to the linker flags suppresses the error. E.g. in the port Makefile: LDFLAGS+= -Wl,--undefined-version For an example, see: <a class="moz-txt-link-freetext" href="https://github.com/freebsd/freebsd-ports/commit/37790b26cbda11cd4bb6f237b86cd94739c4059c">https://github.com/freebsd/freebsd-ports/commit/37790b26cbda11cd4bb6f237b86cd94739c4059c</a> </pre> </blockquote> <p>Thanks very much! That did indeed fix databases/rrdtool and and sysutils/flashrom builds. What is the best way to flag any such issues ? Just open a PR for each individual port ?<br> </p> <p> ---Mike<br> </p> <p><br> </p> <blockquote type="cite" cite="mid:D365EB02-14AC-4F85-B687-962C20A7BA04@FreeBSD.org"> <pre class="moz-quote-pre" wrap=""> </pre> </blockquote> </body> </html> --------------93SDc0twK8siL5B3tOvjiI6a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04837a47-a39c-40c5-a045-2d27fb3893ac>