On Sun, Apr 8, 2018 at 9:51 AM, Albert Graef wrote:
> Thanks, Eli! I'll give it another go immediately.
Worked, thanks again!
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW:https://plus.google.com/+AlbertGraef
On Sun, Apr 8, 2018 at 9:40 AM, Eli Schwartz via aur-general
wrote:
> I've removed it manually, we're looking at a more permanent solution.
Thanks, Eli! I'll give it another go immediately.
Albert
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
W
LoneVVolf wrote:
> AUR has llvm33 , llvm38, llvm39, llvm4 and llvm 5 . Maybe your packages
> can use one of those ?
LLVM 3.5 is the last version which still has the old JIT backend,
which is what Pure still needs right now. LLVM 3.4 would work just as
well, but that's not available in the AUR, and
On 04/08/2018 03:29 AM, Albert Graef via aur-general wrote:
> On Sun, Apr 8, 2018 at 5:56 AM, Eli Schwartz via aur-general
> wrote:
>> Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg
>> sets it from the first element of pkgname, and this is why the .SRCINFO
>> still shows it
On Sun, Apr 8, 2018 at 5:56 AM, Eli Schwartz via aur-general
wrote:
> Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg
> sets it from the first element of pkgname, and this is why the .SRCINFO
> still shows it.
I can add an explicit pkgbase=llvm35 again. (I already tried tha
On 04/06/2018 07:12 AM, LoneVVolf wrote:
> Although SRCINFO does have pkgbase=llvm35 in it, that's not in the
> PKGBUILD. I doubt that's the cause of the issue, but try adding pkgbase
> explicitly to PKGBUILD.
Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg
sets it from the
On 06-04-18 08:11, Albert Graef via aur-general wrote:
The llvm35 package recently got kicked from extra, but I need it for
my Pure package (https://aur.archlinux.org/packages/pure/) which in
turn is needed for a bunch of other packages I maintain in the AUR.
So I resurrected llvm35 from extra,