On Sat, 12 May 2012 03:55:48 +0100 Bruce Dubbs <[email protected]> wrote:
> I've been thinking about this a little more. I see that llvm is an optional > dependency of mesa. What does it add to mesa? I believe Mesa uses it to optimise Gallium 3d http://en.wikipedia.org/wiki/Gallium3D#LLVM_usage > As far as llvm goes, I see several potential options: > > 1. Leave it alone and ignore clang. > > 2. Provide instructions to build llvm/clang with static libraries. > > 3. Provide instructions to build llvm/clang with static and dynamic > libraries. > This is done with './configure --prefix=/opt/llvm --enable-shared' The > executables are then dynamically linked. > > 4. As in 3, but explicitly remove the .a files. `rm /opt/llvm/lib/*.a` after > make install. > > 5. Figure out a way to build llvm/clang with only dynamic libraries. > > I'm leaning towards #3, but would like other opinions. I've not looked at it lately but yes, option 3 looks like the way to go. Except why do we install it into /opt? If you were using it as your C compiler, wouldn't you want its libraries in /usr/lib? Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
