Notice that there's a comment in the PKGBUILD for mesa:

# --with-llvm-shared-libs \ # enabling this would force us to move llvm-amdgpu-snapshot from community to extra, delay it until llvm 3.3 / Mesa 9.2/10.0

If you want the R600 LLVM backend enabled, llvm-amdgpu-snapshot will have to be installed with mesa.

When compiled using llvm-andgpu-snapshot, my vmware guest can't start X with xf86-video-vmware. Change to offical llvm package solved the problem.

I have specificaly created llvm-r600 in AUR because of this. It includes clang, compiler-rt and is from 3.3 svn. I primary use it for OpenCL with R600 which requires mesa to be built against llvm shared libraries. No problems here anymore.

@Armin K.

Only Tom Stellar branch is the only one certified to work with mesa-9.1.x.
Your AUR package is only certifed to work with mesa from the mesa git trunk (9.2-devel).

@Other

I will try to provide mesa packages with tstellar's llvm lib dynamically linked, then let say if it work without regressions.

Yeah, I am aware of that, and I use llvm svn just because I wanted to make Mesa-git package with OpenCL library which has seen some improvements over 9.1. Not so long ago, llvm-r600 was 3.2 with patches from Tom Stellard.

I've also suggested to include *official* Tom Stellard's patches into ArchLinux llvm, but you can see the answer for yourself.

https://mailman.archlinux.org/pipermail/arch-general/2013-March/033029.html

You can use following repo, mesa is built with tstellar's llvm branch. It doesn't conflict with default llvm installation.
Just add this on the top of your pacman.conf repo list:

[mesa-llvm-shared]
Server = http://pkgbuild.com/~lcarlier/mesa-llvm-shared/$arch

Currently only x86_64 is provided.

Thanks for that. Can you provide PKGBUILDs or patches so we can integrate this in our official builds?

The problem we have now is that if we patch our LLVM build with Tom Stellards patches, we will be forced to keep LLVM at 3.2 until Mesa 9.2 gets released. Your solution adds shared libraries to the amdgpu snapshot, which doesn't conflict with our default LLVM build, so your solution is probably the best way to fix this.

I've also pushed the splitted llvm-amdgpu-snpshot package in community repo.

@Jan de Groot

Mesa 9.1.2 can be built with LLVM 3.3svn revision 181113, and I built the package two or three days before 3.3 was branched, so I see no problems why you'd need to wait for Mesa 9.2 to upgrade LLVM to 3.3. When Arch upgraded LLVM to 3.2, Mesa 9.0 needed several upstream patches.

I've used these patches to get 9.1.2 to build against LLVM 3.3svn rev 181113

http://cgit.freedesktop.org/mesa/mesa/patch/?id=ead4db420e9e5408f41c70768a290592a384aedb
http://cgit.freedesktop.org/mesa/mesa/patch/?id=4742f9b00b804dd01eb9955dd386a2373cd8eb36
http://cgit.freedesktop.org/mesa/mesa/patch/?id=6249db73ea580e6a54874235ffb3a7d42ac63bb4
http://cgit.freedesktop.org/mesa/mesa/patch/?id=7cd248aa7938a068663fcd605169b7d4e21636bf
http://cgit.freedesktop.org/mesa/mesa/patch/?id=a0c8942bb4742b4bd22f494cea4dcd59d9ca99ab
http://cgit.freedesktop.org/mesa/mesa/patch/?id=cd84353d576246273d1c6ae8e96b65217be15ebc

My initial suggestion was to split shared llvm library into libllvm package. The pastebin links containing PKGBUILDs in my mailing list RFC are gone though and I don't have them arround anymore.

I will probably implement this for Mesa 9.1.3. Is it a problem if it's going to depend on a community package, or should we move llvm-amdgpu-snapshot to extra for this?

AFAIK, you will have to move the package to extra repo. Dependency on community packages are only allowed for optional dependencies (or building dependencies).

I'm a bit afraid of unwanted side effects. We could have llvm-amdgpu-lib-snapshot and stable llvm on a system at the same time.

/usr/lib/llvm/libLLVM-3.2.so and
/usr/lib/llvm/libLLVM-3.2svn.so.

What side effects? The fact that mesa shrinks to a small package and that we're running a supported configuration should be enough to motivate this change. Apps will most likely never link to two versions of llvm, and in case they do through loading dri drivers, they would crash with the static version anyways.

Please check 9.1.3-1 in testing with llvm-shared-libs enabled - llvm-amdgpu-snapshot has been moved to extra.