The lack of uniformity among arches on RHEL 8 is becoming annoying. The latest one is a head-scratcher: No matching package to install: 'vulkan-devel' Really? RHEL 8 is not shipping vulkan on all arches? Thanks, Michael _______________________________________________ epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...

On Tue, 24 Sep 2019 at 17:18, Michael Cronenworth <mike(a)cchtml.com&gt; wrote: > > The lack of uniformity among arches on RHEL 8 is becoming annoying. > > The latest one is a head-scratcher: > > No matching package to install: 'vulkan-devel' > > Really? RHEL 8 is not shipping vulkan on all arches? > The only vulkan-devel I see in RHEL-8 is ./x86_64/RHEL-8-001/non_modular/mesa-vulkan-devel-18.3.1-5.el8_0.x86_64.rpm so s390x, aarch64 and ppc64le do not have it. [smooge@batcave01 latest]$ find . -type f -print | grep vulkan ./x86_64/RHEL-8-001/non_modular/mesa-vulkan-devel-18.3.1-5.el8_0.x86_64.rpm ./x86_64/RHEL-8-001/non_modular/mesa-vulkan-drivers-18.3.1-5.el8_0.x86_64.rpm ./x86_64/RHEL-8-001/non_modular/vulkan-headers-1.1.101.0-1.el8_0.noarch.rpm ./x86_64/RHEL-8-001/non_modular/vulkan-loader-1.1.101.0-0.el8_0.x86_64.rpm ./x86_64/RHEL-8-001/non_modular/vulkan-loader-devel-1.1.101.0-0.el8_0.x86_64.rpm ./x86_64/RHEL-8-001/non_modular/vulkan-tools-1.1.101.0-1.el8_0.x86_64.rpm ./x86_64/RHEL-8-001/non_modular/vulkan-validation-layers-1.1.101.0-1.el8_0.x86_64.rpm so it looks like vulkan is only for x86_64 and no they did not ship the development packages. I believe this is one of those.. will need to be a module. > Thanks, > Michael > _______________________________________________ > epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org > To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj... -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...

On 9/24/19 4:41 PM, Troy Dawson wrote: > Actually, looking closer, there is not package called "vulkan". > So, not having 'vulkan-devel' is very logical. > > For RHEL8 vulkan synced with F29, which split it's packaging up. In > vulkan's place is > > vulkan-headers > vulkan-loader > vulkan-tools > vulkan-validation-layers > > So, look what you would use in Fedora right now, and use the > appropriate package(s) Yes, the 'vulkan' package has seen some interesting package splitting over the years. Today, vulkan-devel is a virtual provides by vulkan-loader. The 'vulkan-loader-devel' package is what I really want, but that package is not provided in aarch64 either. What now?