Date: Tue, 30 Nov 2021 14:03:14 +0100 From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= <mgorny@moritz.systems> To: "Floyd, Paul" <paulf2718@gmail.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@FreeBSD.org> Subject: Re: llvm/clang upstream Message-ID: <308f3c42a357e6be288e01060868fa7b003ced4b.camel@moritz.systems> In-Reply-To: <bb0b1201-291d-1483-080c-d771091329a3@gmail.com> References: <43a13a6b-baee-e8cb-3624-ee98da510ad0@gmail.com> <0E4F98DC-1B05-4E1C-813F-4246C45E9C85@FreeBSD.org> <bb0b1201-291d-1483-080c-d771091329a3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2021-11-30 at 13:22 +0100, Floyd, Paul wrote: > > > It would be nice to be able to just 'git clone && cmake && make' > > > (roughly speaking). > > I do this all the time. What seems to be the problem? > > Now that I'm looking at this again, I think that the problem was that > when I first set up llvm builds I wrote a couple of scripts to run > cmake > and then to run make. The cmake config script might now be out of > date. > > When running make I get an error finding unwind.h. > > So my guess us that building libcxxapi without libunwind is broken but > either not building libcxxapi or building it with libunwind works. Please note that the "official" way of building stuff has changed a few times, so you might be using an outdated approach. I think the current way of building runtimes is via LLVM_ENABLE_RUNTIMES. -- Best regards, Michał Górny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?308f3c42a357e6be288e01060868fa7b003ced4b.camel>