Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Nov 2014 01:03:18 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-x11@FreeBSD.org
Subject:   [Bug 182723] graphics/dri fails to build on 9.2-Stable
Message-ID:  <bug-182723-8047-Vr21hNEJBN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-182723-8047@https.bugs.freebsd.org/bugzilla/>
References:  <bug-182723-8047@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182723

--- Comment #7 from C Hutchinson <portmaster@bsdforge.com> ---
(In reply to Jean-Sebastien Pedron from comment #5)
> (In reply to C Hutchinson from comment #4)
> > Just so you know; I'm not a GNU C zealot.
> > It was just my understanding the FreeBSD supported *both* gcc,
> > and clang/llvm, as the tool-chain in base. Given that clang/llvm is
> > *much* larger, and as such, slower for (initially) building/installing
> > kernel/world. I chose gcc on a fresh install. Thinking I could
> > add clang/llvm later, and into userland. After 3 days of investigating
> > all of this. I have discovered all of this to be untrue.
> 
> I can't comment on other ports, but on the particular case of Mesa, GCC
> 4.2.1 from base is unable to build Mesa because it's too old (the "invalid
> suffix on integer" error you got).
> 
> A modern GCC will build Mesa properly. You could put "USE_GCC=yes" globally
> in the Makefile (ie. regardless of any .if block). But this isn't very user
> friendly: there may be a way to tell "I want to use GCC for all ports" in
> /etc/make.conf but I don't know it.
My understanding for "global" declaration, is to use:
FAVORITE_COMPILER=gcc
But there are other "knobs" as well; BOOTSTRAP, CXX, {...}.
Anyway. I *ultimately* found it all to be too expensive, for too little
gain. :)
> 
> In all cases, Mesa requires LLVM and Clang to build some parts of the
> Gallium drivers. For instance, the GLSL engine of the Radeon drivers is
> based on LLVM, no matter the compiler used to build the libraries. When the
> libOpenCL.so port will be ready for the Ports tree, it will depend on LLVM
> too. In both cases, LLVM is used here for its framework beyond the sole
> C/C++ compiler.
Sure. Makes sense.
Thank you very kindly, for your thoughtful reply.

--Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-182723-8047-Vr21hNEJBN>