Comment 9 for bug 1371636

(In reply to comment #4)
> I tested it with LLVM 3.4.2 and the same set of gcc-4.9.2 (svn) and binutils
> (svn) used to open this bug report and all built fine.
It may be that llvm 3.5 + mesa is "using" gcc/binutils in a slightly different way.
Can you try using the same versions as the one I've listed ? This way if it works one can start looking for the combination that exhibits the problem.

> So for me it looks
> like that LLVM 3.5.0 came with something changed. Is it not a same name of
> some function, introduced in LLVM 3.5.0 and present in Mesa before?
If the function prototype has changed then a compiler warning is due. Afaict your issue is at a later stage - link time.

> It seems to not be LTO issue if Kai really not uses it and with LLVM 3.4.2
> it builds with LTO for me.
I would recommend disabling LTO until one is able to clearly establish the root cause. After it's sorted you can get it back on for llvm.

> I checked content of ld/emultempl/elf32.em in my git replica and patch you
> are reffering to is incorporated.
I would recommend that you try the patch, before doing anything.