Date: Thu, 16 May 2019 10:30:13 +0200 From: Niclas Zeising <zeising+freebsd@daemonic.se> To: Thomas Mueller <mueller6722@twc.com>, freebsd-current@freebsd.org Subject: Re: Inability to build FreeBSD-current amd64 Message-ID: <3e65a762-ce32-c1df-8f89-8545538ab521@daemonic.se> In-Reply-To: <d635d81c-3077-9f26-6a13-68c7a7d222d0@daemonic.se> References: <201905152326.x4FNQ8up005043@ilsoft.org> <6fd6988399603ec68520cec45dff7590ef190a8d.camel@freebsd.org> <d635d81c-3077-9f26-6a13-68c7a7d222d0@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-05-16 09:36, Thomas Mueller wrote: > from Niclas Zeising: > >> I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if >> that's what you're asking about. > >> This won't take away the need for llvm ports in certain ports builds, however, >> such as firefox and mesa. > > So now I wonder why I failed four times straight building current. One definition of insanity is doing the same thing repeatedly and expecting a different result. > > Maybe the build host, 11.1-STABLE from July 30, 2017, was too old? I wouldn't have thought it was too old. > > I could also try an old current host from August 2, 2017, or try to build 12-STABLE from my 11.1-STABLE host. Would I do better to build amd64 or i386 from amd64 host? I presently have no FreeBSD i386 installation, only amd64. > That could be that the toolchain on 11.1 stable is too old to build current. If you've posted the error you're getting, I've missed it, however. Regards -- Niclas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e65a762-ce32-c1df-8f89-8545538ab521>