Mesa LLVM clang libclc -- make sure they are consistent

derk

This is an information post.. for those experiencing issues with llvm, clang, libclc and mesa interactions.

I had a problem today where on the same machine but two different environments (different root partitions) which are almost the same but not quite..

Recently to save time, I built llvm in one environment , quickpkg'd it and installed on the other ..rebuilt clang there as well .. today I ran an upgrade in this as a chroot'd instance .. but mesa failed to build .. actually it looked very much like a linking error .. i915_pipe.la failed to build .. also c++11 warningstrying to link to an obsolete/missing version of the C++ library.

in the master environment mesa installed fine .. so something was inconsistent .. decided to rebuild llvm, clang and libclc in the chroot'd instance .. after that mesa built and installed fine.

So .. make sure .. llvm, clang and libclc are built with the same environment to prevent issues .. particularly with linkage.

bschnzl · Tux's lil' helper Joined: 13 Mar 2005 Posts: 94

This looked like another circular block...

So I did:

derk · Posted: Wed Apr 20, 2016 2:33 pm Post subject:

so looks like you have really old llvm and clang installed .. then upgrade is required to meet mesa 11.2.1 requirements .. maybe do llvm upgrade first then mesa install ..

how did you manage to keep from upgrading in previous rebuilds of llvm and clang ??

ah.. a newer libclc-0.2.0_pre20160209 would help .. are you on stable ?? with some ~arch (unstable)

perhaps you have accidently added llvm, clang, libclc and/or mesa to your world file .. that will mess-up dependancy resolution ..

do an " emerge -n --deselect=y <offending packages here>"
to remove them from your world file
.. anything that pulls in xorg-server will pull in the above as well .. so they don't need to be in world

bschnzl · Tux's lil' helper Joined: 13 Mar 2005 Posts: 94

I emaint -r gentoo sync about once a week, manually on this box. It is my primary lappy, so it gets picked for most of the adventures. I have some ~amd64, and well - you spotted them.

<brag>
It is a relatively new monster, w/ a 1TB hybrid drive and a 2TB hard drive. I run xen, usually getting to 3 HVM doze instances, and a PV *NIX or two thrown in for good measure.
</brag>

I found mesa worked best for multimedia support when I was given a video forensic case. I used transform to pull an avi out of a "proprietary" format. I tried several video editing packages, but all were in the portage tree.

I still don't have OpenGL (nvidia)... but I beat all comers nonetheless...

So... for day to day Ops, which package can I drop?
_________________
Persistance Pays

derk · Posted: Thu Apr 21, 2016 11:24 am Post subject:

you will have to decide if the most recent mesa is important and keyword it's dependencies as needed .. mixing arch and ~arch is tricky and each set-up is unique .. so you are on your own .. experiment with setting all of mesa , llvm, clang and libclc keyworded as ~arch .. other stuff may need setting as well .. have fun !

bschnzl · Tux's lil' helper Joined: 13 Mar 2005 Posts: 94

Whats even trickier (word?) is backing out ~arch after a regular update demands it.

I have run Gentoo long enough to understand the requirements for inclusion in the dev group, and the testers group. This a 'UGE undertaking, and only the dedication of some highly skilled individuals makes it possible. For that, I can only offer thanks.

With the thousands of packages, and the complex environments, it is truly amazing that Gentoo worx. Thank You all.

That being said, fun is not a word I would use to describe these blocks. Just call this post another Quality Assurance Flag - where ever the issues starts.

The answer here was to ~arch clang, llvm and libclc, and run