[Bug 182723] graphics/dri fails to build on 9.2-Stable
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 17 18:41:14 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182723
--- Comment #4 from C Hutchinson <portmaster at bsdforge.com> ---
(In reply to Jean-Sebastien Pedron from comment #3)
> The original problem is fixed in the Ports tree.
>
> (In reply to C Hutchinson from comment #2)
> > This is for those of us who use gcc && not clang :)
> >
> > However, this doesn't fix more recent versions of graphics/dri
> > that are built on (recent) 11-CURRENT. As the conditional won't
> > see 11. :(
> > I was also unable to build graphics/dri under _any_ circumstances
> > on 11-CURRENT. Even if making the conditional recognize 11.
> > I'll submit a separate pr(1) for it. :)
>
> I don't know what is the proper way to explicitely indicate that all ports
> should be built with GCC instead of the clang.
>
> Why do you need GCC in this case?
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. FreeBSD
*currently* doesn't support gcc as the tool-chain, w/o a *great* deal
of "dancing", or "hoop jumping", and even then; not *likely* for
kernel.
Not *really* complaining, per se; just saying. So you'd understand
why I was using gcc4* on a new system. :)
Hope I answered your question. :)
Thanks.
--Chris
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-x11
mailing list