Luchesar ILIEV

@cippaciong Unless you have reasons to believe that the failure might be caused by the Arch environment specifically, I'd suggest just commenting out the `make check` commands from the PKGBUILD.

@hesiod Thank you very much for the pull request. I know libc++ is important for some people, but unfortunately I've never been able to invest more time in acquainting myself...

@brunocodutra Yup, I noticed that on aur-general too and was thinking along the same lines as you. Unfortunately, I've been rather busy with other things recently, so I even haven't...

I've updated the patch, but the web editor produced a merged commit that'll probably make the history a bit hard to follow. I'll look into this again when we decide...

The discussion continues in #10.

> Lord Heavy's llvm-libs-svn doesn't conflict with llvm-libs , if his method works for aur llvm-svn there's no need for a compat pacakge. Thanks, Lone_Wolf! Indeed, it boils down to...

Here's one possible solution: let's imagine that we keep the current packages as they are, but also introduce a new one, say `llvm-libs-lite-svn`, which will include _only_ the versioned libs...

NB: 7eda367f5744f5dfc55d45ed4d09fc436a0f16e8 fixed the required python-sphinx package: the original PKGBUILD listed the python3 version as a dependency.

The bug hasn't shown up for a long time since the Python dependency was fixed, so I'm going to assume that it's gone for good.

@kode54 Thank you very much for your report. I'll have a look into it.