I ended up having to use `env LLVM_CONFIG=llvm-config-3.9` in order to get it to compile. After installing it, I think it loaded up properly. I couldn't get Vulkan examples ( <a href="https://github.com/SaschaWillems/Vulkan">https://github.com/SaschaWillems/Vulkan</a> ) to work, though; it was saying "Unsupported driver". So I played around the files, trying to get it work, rebooted the system and found out I had broken it completely, because the login screen didn't even show up. I guess I'll just wait for the "official" RADV release. Oh, well.<div><br></div><div>Thanks,</div><div>Jakub "Limeth" Hlusička</div><div><br>
On So, říj 1, 2016 at 11:01 , Gustaw Smolarczyk <wielkiegie@gmail.com> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">I don't think your fix with the symlinks is correct. You've just
worked-around one part of the problem (missing include directories)
leaving the total lack of detection of llvm alone. Now you lack the
HAVE_LLVM define that should be automatically created by the build
system if it recognizes llvm correctly. Without it, the source code
references the already non-existing R600 target, since it doesn't know
which llvm version it deals with. After that you will lack the library
references, and maybe other llvm-specific compilation options. Trying
to work-around all that seems counterproductive.
Do you have the llvm development package (I think it's called llvm-dev
or libllvm-dev on ubuntu) installed? It seems that configure cannot
find the llvm-config binary. It should probably be in /usr/bin.
2016-10-01 18:44 GMT+02:00 Limeth <<a href="mailto:jakub.hlusicka@email.cz">jakub.hlusicka@email.cz</a>>:
<blockquote> I have found out that the llvm-3.9 installation directory in Ubuntu is not
as you said and ended up creating symlinks to it:
```
sudo ln -s /usr/include/llvm-3.9/llvm/ /usr/include/llvm
sudo ln -s /usr/include/llvm-c-3.9/llvm-c/ /usr/include/llvm-c
```
Now I seem to be getting a different error:
```
ac_llvm_util.c: In function ‘ac_init_llvm_target’:
ac_llvm_util.c:13:2: error: implicit declaration of function
‘LLVMInitializeR600TargetInfo’ [-Werror=implicit-function-declaration]
LLVMInitializeR600TargetInfo();
^
ac_llvm_util.c:14:2: error: implicit declaration of function
‘LLVMInitializeR600Target’ [-Werror=implicit-function-declaration]
LLVMInitializeR600Target();
^
ac_llvm_util.c:15:2: error: implicit declaration of function
‘LLVMInitializeR600TargetMC’ [-Werror=implicit-function-declaration]
LLVMInitializeR600TargetMC();
^
ac_llvm_util.c:16:2: error: implicit declaration of function
‘LLVMInitializeR600AsmPrinter’ [-Werror=implicit-function-declaration]
LLVMInitializeR600AsmPrinter();
^
cc1: some warnings being treated as errors
```
Full log: <a href="http://pastebin.com/QgyQdX0r">http://pastebin.com/QgyQdX0r</a>
After further investigation, I've found that this error resides in
RADV-specific source code; now I'm on my own. I will proceed to revert to
older, working commits on that branch.
Thank you for the help everyone, much appreciated!
Jakub "Limeth" Hlusička
On So, říj 1, 2016 at 5:29 , Bas Nieuwenhuizen <<a href="mailto:bas@basnieuwenhuizen.nl">bas@basnieuwenhuizen.nl</a>>
wrote:
Hi, Do you have LLVM development packages installed? It seems configure
can't find llvm-config and the header that can't be found is in the standard
include path, at least for archlinux (i.e.
/usr/include/llvm-c/TargetMachine.h). radv needs LLVM 3.9 development
packages or newer. The issue Gustaw referred to is probably the cause of
configure not giving an error about it. If you want to be sure this is
handled right, also enable radeonsi to be build. Yours sincerely, Bas
Nieuwenhuizen On Sat, Oct 1, 2016 at 2:23 PM, Limeth
<<a href="mailto:jakub.hlusicka@email.cz">jakub.hlusicka@email.cz</a>> wrote:
Hello, I decided to try out the work-in-progress AMD driver with Vulkan
support: <a href="https://github.com/airlied/mesa/tree/semi-interesting">https://github.com/airlied/mesa/tree/semi-interesting</a> But when I
try to compile the source, it fails -- see the log:
<a href="http://pastebin.com/1nCQYCEF">http://pastebin.com/1nCQYCEF</a> Is this a common problem with the official
mesa3d repo aswell, or is it RADV-specific? How can I resolve this? Thank
you, Jakub "Limeth" Hlusička _______________________________________________
mesa-dev mailing list <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a>
_______________________________________________
mesa-dev mailing list
<a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a>
</blockquote>_______________________________________________
mesa-dev mailing list
<a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a>
</div></blockquote><br><br>
</div>