On Sun, 1 Apr 2012 17:57:31 -0600 (MDT)
Warren Block wrote:
> On Sun, 1 Apr 2012, Conrad J. Sabatier wrote:
>
> > On Sun, 1 Apr 2012 14:11:29 -0500
> > "Conrad J. Sabatier" wrote:
> >
> >> On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
> >> Warren Block wrote:
> >>>
> >>> Have you tried clang with cc
On Sun, 1 Apr 2012, Conrad J. Sabatier wrote:
On Sun, 1 Apr 2012 14:11:29 -0500
"Conrad J. Sabatier" wrote:
On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
Warren Block wrote:
Have you tried clang with ccache? Any tricks?
No, I haven't tried that. Actually, I don't believe I've ever even
tried
On Sun, 1 Apr 2012 14:11:29 -0500
"Conrad J. Sabatier" wrote:
> On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
> Warren Block wrote:
> >
> > Have you tried clang with ccache? Any tricks?
>
> No, I haven't tried that. Actually, I don't believe I've ever even
> tried using ccache at all (at least, no
On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
Warren Block wrote:
>
> Have you tried clang with ccache? Any tricks?
No, I haven't tried that. Actually, I don't believe I've ever even
tried using ccache at all (at least, not that I can recall). :-)
--
Conrad J. Sabatier
conr...@cox.net
___
On Sun, 1 Apr 2012, Conrad J. Sabatier wrote:
I can well understand your hesitation. I didn't jump on the clang
bandwagon for a good while myself, either.
But, from examining and comparing clang's assembly language output
against gcc's, it does seem pretty apparent that clang produces
some pre
On Sun, 1 Apr 2012 09:06:08 -0400
Robert Huff wrote:
> Conrad J. Sabatier writes:
>
> > Note, too, that none of these exceptions have anything to do with
> > my /usr/src builds. I've been using clang for buildworld and
> > buildkernel for quite some time now.
>
> I've heard that, but
Conrad J. Sabatier writes:
> Note, too, that none of these exceptions have anything to do with
> my /usr/src builds. I've been using clang for buildworld and
> buildkernel for quite some time now.
I've heard that, but I think I'll wait until it becomes the
official default. :-)
>
On Sat, 31 Mar 2012 11:11:25 -0400
Robert Huff wrote:
>
> As long as we're talking about clang, I have two questions.
> 1) Is there any generic reason why a port compiled with clang
> won't work on a world compiled with gcc?
No, none that I'm aware of. I've occasionally seen mentio
/etc/make.conf :
.if !empty(.CURDIR:M/usr/ports/*)
.endif
clang for ports, YMMV as always.
http://wiki.freebsd.org/PortsAndClang
"libreoffice 3.5.x builds and run sucessfully
with clang 3.0 and (upcoming) 3.1" - @bapt
So wait for libreoffice 3.5 for clang support.
--
View this message in
As long as we're talking about clang, I have two questions.
1) Is there any generic reason why a port compiled with clang
won't work on a world compiled with gcc?
2) If not, how do I set that up?
Robert Huff
___
10 matches
Mail list logo
