Package Details: compute-runtime 18.32.11249-1

Git Clone URL: (read-only)
Package Base: compute-runtime
Description: Intel(R) Graphics Compute Runtime for OpenCL(TM). Replaces Beignet for Gen8 (Broadwell) and beyond. Weekly build version.
Upstream URL:
Keywords: intel intel-compute-runtime neo opencl
Licenses: MIT
Conflicts: compute-runtime-git
Provides: opencl-driver
Submitter: grmat
Maintainer: grmat (jdanecki)
Last Packager: grmat
Votes: 2
Popularity: 0.916515
First Submitted: 2018-05-24 21:39
Last Updated: 2018-08-17 10:53

Required by (12)

Sources (7)

Latest Comments

1 2 3 4 Next › Last »

grmat commented on 2018-07-23 14:20

OK, I somehow thought it would not make sense to add deps also required by base-packages, but of course it makes sense, because people can uninstall packages from base...

ArchangeGabriel commented on 2018-07-23 11:29

namcap warnings are not about makedepends but actual depends, so they should be added.

jdanecki commented on 2018-07-20 16:38

I'd zlib, ncurses, base-devel already installed before running namcap.

grmat commented on 2018-07-20 15:46

Both are covered implicitly as dependencies of multiple packages in base-devel or even base. Have you called namcap before installing base-devel?

jdanecki commented on 2018-07-20 13:29

What about adding zlib and ncurses to satisfy namcap:

compute-runtime E: Dependency zlib detected and not included (libraries ['usr/lib/'] needed in files ['usr/lib/', 'usr/lib/'])
compute-runtime E: Dependency ncurses detected and not included (libraries ['usr/lib/'] needed in files ['usr/lib/'])

They are not part of base-devel.

ArchangeGabriel commented on 2018-07-18 21:25

@jdanecki No, building with clang is perfectly fine. What is import is to build with repo clang (which is 6.0.1 atm), and to respect {C,CXX,LD}FLAGS. ;)

And @grmat is right regarding base-devel, maybe you should install this in your docker image.

grmat commented on 2018-07-17 16:27

OK, I'll add you then.

I've let those deps out deliberately, because they're all in base-devel. Quoting the Wiki on packaging:

Note: The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array.

jdanecki commented on 2018-07-17 15:35

@MichaelChou I've built this package in fresh docker container with Arch without problems. We have similar issue reported on github: Can you provide more details how did you reproduce this issue?

@grmat I thought about platform, when I can test building of binary packages instead of local system. As you've mentioned earlier we're not ready yet to be included in community repo, so lets decide later who should maintain it, when we have something to submit. You can add me as co-maintainer, so we can together work on this package. In my docker tests with this package I've found we should add: "gcc make patch bison flex pkgconf" packages to makedepends list. In case of gcc, if you want to build Neo with clang instead of gcc, you can add: "-DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++" to cmake parameters.

@ArchangeGabriel Is there any requirement in Arch, that new package should be compiled with gcc instead of clang?

MichaelChou commented on 2018-07-15 08:28

I used to compile this without any problems. But now it seems something's missing:

/tmp/makepkg/compute-runtime/src/neo/runtime/helpers/hw_info.h:24:10: fatal error: igfxfmid.h: No such file or directory
  #include "igfxfmid.h"
compilation terminated.

grmat commented on 2018-07-14 11:01

Well then, of course it makes sense.

Not sure what you exactly mean. Yes, there is the Arch Build system, it's mainly the official repos, PKGBUILDs and makepkg. And there is the AUR, which is a collection of user-supplied PKGBUILDs, just like this one.

If you mean a platform with build servers providing automated builds for the AUR, I'm afraid it doesn't exist. Only for Trused Users/Arch contributors. Once this gets compatible with the official repos, it should be possible to use the infrastructure. There is a community-testing repo as well but you should contact them or at least a Trusted User like ArchangeGabriel about this.

By the way, if you feel like you should maintain this submission, just tell me. I can add you as co-maintainer or transfer ownership, so you could update this package as you like. I'm really just a user who wanted to use Neo, created a PKGBUILD for that reason and wanted to share it. I just don't want to add you without your approval.