Date: Wed, 9 Mar 2022 13:45:44 -0800 From: John Baldwin <jhb@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 7ecd99fa424d - main - Build compiler-rt against libunwind, not libcxxrt Message-ID: <1eb62898-4f0a-504f-26a8-ee01c46093a6@FreeBSD.org> In-Reply-To: <202203092130.229LUKFS011484@gitrepo.freebsd.org> References: <202203092130.229LUKFS011484@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/9/22 1:30 PM, Dimitry Andric wrote: > The branch main has been updated by dim: > > URL: https://cgit.FreeBSD.org/src/commit/?id=7ecd99fa424df001028c5cddc52d25b29232f1af > > commit 7ecd99fa424df001028c5cddc52d25b29232f1af > Author: Dimitry Andric <dim@FreeBSD.org> > AuthorDate: 2022-03-09 21:23:35 +0000 > Commit: Dimitry Andric <dim@FreeBSD.org> > CommitDate: 2022-03-09 21:23:35 +0000 > > Build compiler-rt against libunwind, not libcxxrt > > Parts of compiler-rt are also built for libgcc_eh and libgcc_s, and > these were already pointing to the libunwind unwind.h. For the sake of > consistency, also build compiler-rt itself against the libunwind > unwind.h, not the libcxxrt one. Do we even need the explicit -I at all now that we install unwind.h into /usr/include? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1eb62898-4f0a-504f-26a8-ee01c46093a6>