Summary: | LLVM 3.8(svn): llvm changes llvm-config output again? | ||
---|---|---|---|
Product: | Mesa | Reporter: | Krzysztof A. Sobiecki <sobkas> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED NOTOURBUG | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | lowest | CC: | lorenz.bona, sobkas, sylvestre |
Version: | git | ||
Hardware: | All | ||
OS: | All | ||
URL: | https://llvm.org/bugs/show_bug.cgi?id=24333 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | A patch? |
Description
Krzysztof A. Sobiecki
2015-07-26 15:07:43 UTC
(In reply to Krzysztof A. Sobiecki from comment #0) > Created attachment 117384 [details] [review] [review] > A patch? > > LLVM 3.8(svn): llvm-config-3.8 output for "--version" have "svn" in it, but > shared library filename doesn't have it. For reasons? Thank you, with your patch I can build mesa again with llvm 3.8. https://bugs.freedesktop.org/show_bug.cgi?id=91456 *** Bug 91456 has been marked as a duplicate of this bug. *** Please send the patch to mesa-dev (ideally using git send-email). It'll get wider exposure there. Please note that autotools buils have the "svn" part in the libname. I don't knows if it will be deprecated in 3.8 and remove later or if it will be removed in 3.8. (In reply to Serge Martin from comment #4) > Please note that autotools buils have the "svn" part in the libname. > I don't knows if it will be deprecated in 3.8 and remove later or if it will > be removed in 3.8. I use packages from: deb http://llvm.org/apt/unstable/ llvm-toolchain main And it have a wonderful patch called: strip-svn.diff Guess what it does... (In reply to Emil Velikov from comment #3) > Please send the patch to mesa-dev (ideally using git send-email). It'll get > wider exposure there. I don't see how It would be appropriate to even try to include it into a main tree, so no. (In reply to Krzysztof A. Sobiecki from comment #6) > (In reply to Emil Velikov from comment #3) > > Please send the patch to mesa-dev (ideally using git send-email). It'll get > > wider exposure there. > > I don't see how It would be appropriate to even try to include it into a > main tree, so no. Had not idea that the llvm builds are inconsistent (again). So yes, with that into account I fully agree that we shouldn't apply until llvm is sorted. I was trying to contact maintainer of http://llvm.org/apt/unstable/, now I will fill a bug on llvms bugzilla. So I have filled a bug with LLVM: https://llvm.org/bugs/show_bug.cgi?id=24333 Packages on llvm.org/apt should be fixed now, no need for a patch. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.