Mesa-25.0.7-3.el9_7.src.rpm fails to build for me

Rocky Linux Help & Support
1

I’m unable to build this package from source either using mock or rpmbuild. I have the contents of the /var/lib/mock/rocky+epel-9-x86_64/result directory (i.e. the logs) but can’t see how to make them available to you. (The corresponding 9.6 version of the package builds fine using mock.)

Could somebody please check that they are able to build it ? (Otherwise one wonders how the resulting x86_64 packages were built - but still, please could somebody check ?)

With thanks in advance, Roger.

2

It would be helpful to know the errors you’re running into as well as the custom changes you may be making to the RPM spec file.

I ran a scratch build here and mesa, as we ship it, builds fine in our environment.

3

Louis,

Thank you for your extremely helpful reply which has solved my problem.

  1. As it wouldn’t build with my patch in place, I had already tried it as it came from the repo, and it still wouldn’t build.
  2. I would have attached the build logs so that you could see exactly what was going on, but couldn’t work out how to do that. I wasn’t even sure whether attaching them to an email reply would work. Can you tell me how I’m supposed to get a .tar.gz file to attach to a post ? Or to get it to you in some other way ?
  3. From the installed package list in your build log and that in my build log I could see that the problem was likely to be that the repos were dishing up spirv-headers-devel-1.5.5-6.el9.noarch.rpm whereas you were using spirv-headers-devel-1.5.5-10.el9.noarch.rpm .
  4. On looking at the Rocky Linux Repository website one can see that the -10 release is there,(and has been for six weeks or so) but yet it is not being served up by the repos.
  5. On using the -10 release the mesa-25-… package builds fine.

So thank you very much for your help. All that remains is for somebody to work out why the repos are serving up the wrong release of the spirv-headers-devel package.

Happy Christmas ! Roger.

4

Louis,

The reason for the repo serving up the wrong version: yum is looking for spirv-headers-devel on the epel repo, unless I explicitly enable the devel repo. The version in the devel repo is the correct -10 release, while the epel repo has the -6 release.

What should I do about this ?

Thanks, Roger.

5

Don’t use EPEL unless absolutely necessary. Use the standard rocky-9-x86_64 profile and enable devel.

6

Thank you. But I meant more “Should I get EPEL to update their out of date package, and if so how ?”.

But given what you say, another question: As you know, the devel repo gives a warning not to leave it enabled. This is presumably to guard against some particular danger that others have come a cropper on. Do you know what that danger is ?

7

The devel repo has binaries that are in development and should not be used on a production system unless “you” are asked to to solve a particular issue. Allowing un-restricted arbitrary updates from this source could break you system in un-recoverable fashion.

8

I had a problem running a later upstream 6.18 kernel I buillt on the Rocky 9 host using a mock chroot to build mesa

lto1: internal compiler error: Segmentation fault
I switched back to rhel 9 stock kernel and built fine