On Fri, Mar 04, 2016 at 09:53:08AM -0500, Kevin P. Neal
wrote:> On Fri, Mar 04, 2016 at 02:22:26PM +0000, Brooks Davis wrote:
> > On Thu, Mar 03, 2016 at 08:45:05AM -0500, kpneal at pobox.com wrote:
> > > I notice on 10.2 we're using "FreeBSD clang version
3.4.1". But there are
> > > bugs in this version of clang that I'm having trouble with.
> > >
> > > Is compiling a newer (say, 3.7.1) version of clang to target
FreeBSD
> > > supported? I have no desire to replace any of the libraries, just
the
> > > compiler itself. Is that supposed to work _without_ going through
the
> > > ports/pkgs system?
> > >
> > > IOW, can I just download from llvm.org the clang+llvm source,
compile
> > > it on FreeBSD, and then use it safely?
> >
> > It should. The ports don't include many patches.
>
> Yeah, I was just looking at the patches we do include. One of them it looks
> like causes some of the llvm.org-provided includes to not be installed.
>
> I'm not sure I can, well, not install them because I also need to use
the
> same install to do cross compiles. A quick check shows that those includes
> are used when targetting cross and native.
>
> Am I correct about the include files? And, if so, are there plans to
> upstream patches so the llvm.org includes will work out of the box for
> FreeBSD-hosted-and-targetted compiles?
The std*.h include files included with clang are broken on FreeBSD. On
one has stepped forward to fix them so you will have to chose between
installing them and bening able build FreeBSD. In practice, you should
still be able to cross compile if you have a working sysroot for your
target.
-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20160307/f13e1458/attachment.sig>