Unexpected dependencies of graphics/libGL

Manfred Antar null at pozo.com
Tue Jan 19 07:05:35 UTC 2016

> On Jan 18, 2016, at 8:49 PM, Luís Fernando Schultz Xavier da Silveira <schultz at ime.usp.br> wrote:
> Begin forwarded message:
> Date: Sun, 17 Jan 2016 03:19:23 +0000
> From: Luís Fernando Schultz Xavier da Silveira <schultz at ime.usp.br>
> To: freebsd-questions at freebsd.org
> Subject: Unexpected dependencies of graphics/libGL
> Hello,
> Since the beginning of this year, graphics/libGL and friends started
> depending on a significant amount of software, including git and bzr.
> Could anyone explain why that is and whether it is possible to avoid
> such dependencies?
> Also, there is a dependency on clang and llvm from ports because of
> advanced features that I (and I guess many of us) do not require.
> I believe it has to do with the Gallium driver and OpenCL.
> Just a suggestion: it would be pretty nice if there were some port
> knobs to avoid pulling in another toolchain from ports to build
> software that is never run.
> Thank you,
> Luís Fernando

As an added note
the new dependencies also break the build on Sparc64
clang will not build on Sparc64 although llvm will.
So i’m stuck with the earlier version of dri libGl etc.
If there was a way to turn off the depend on clang llvm it would be nice.

More information about the freebsd-ports mailing list