akilgus wrote almost 5 years ago

Is there any chance to get the build for 13.2 fixed in this repository? There seems to be no unresolvable technical show stopper: https://build.opensuse.org/package/show?project=home%3Aaevseev&package=Mesa

sndirsch wrote almost 5 years ago

Of course this would be possible despite openSUSE 13.2 will be out of support pretty soon. Seems you removed U_cso-don-t-release-sampler-states-that-are-bound.patch. Not sure why? For the additional patch fix-missing-memfd-header.patch, please follow our X11:XOrg patch guidelines. After resolving this you can open a submitrequest against X11:XOrg. Thanks!

akilgus wrote almost 5 years ago

I did neither remove anything nor add any patch - you seem to mistake me for the maintainer of the repository I mentioned. My motivation for asking is simply not to let increase the number of repositories I use (currently 49 and counting) any further by adding another "home/" repository for packages at least theoretically already available in a repository in use.

---

sndirsch wrote almost 5 years ago

Indeed I assumed this would be your repository.

akilgus wrote over 4 years ago

Thanks for having revivified providing updated packages for 13.2.

alvarex wrote over 4 years ago

will this bump to version 17.1?

avindra wrote about 4 years ago

17.2.3 release is cut https://github.com/mesa3d/mesa/releases/tag/mesa-17.2.3

blachner wrote over 3 years ago

Could the build be enabled for openSUSE Leap 42.3 to get a Mesa 18 version for this distribution?

sndirsch wrote over 3 years ago

Currently it's not possible, since llvm cannot be built for openSUSE 42.3. :-(

---

blachner wrote over 3 years ago

OK. Thank you for your answer.

Do you think it would be possible to build it anytime soon for openSUSE Leap 42.3? Or will it stay at the current offered Mesa version for this distribution?

---

sndirsch wrote over 3 years ago

I can't say. A collegue is/was working on this. But it has no high priority.

---

mimi_vx wrote over 3 years ago

probably not, Newer versions of Mesa also need new version of Wayland libs and protocols. + Bonus six months after the release of Leap 15.0, 42.3 Leap will EOL

sndirsch wrote over 3 years ago

Ok. Build against Leap 42.3 is enabled in X11:XOrg again. Looks good so far.

_nobody_ wrote about 3 years ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote about 3 years ago

On my TODO list ...

_nobody_ wrote about 3 years ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote about 3 years ago

Looks like this came in with some autocommit magic crap back from factory. :-(

---

r773 | buildservice-autocommit | 2018-09-18 09:37:23 | 0273904b5d3bac6a229ef7bd5bf12077 | unknown | rq635013

baserev update by copy to link target

r772 | buildservice-autocommit | 2018-09-11 15:12:48 | 04666deac08cb6669a4cfb681e18d754 | unknown | rq631796

baserev update by copy to link target

Fortunately Tobias Klausmann brought this back, now to 18.2.1 ...

KhazAkar wrote almost 3 years ago

Please add GALLIUM_HUD support for intel drivers

sndirsch wrote almost 3 years ago

Intel drivers aren't using gallium at the moment. Not sure what you mean here.

Guillaume_G wrote over 2 years ago

Please check/fix %arm and aarch64 before pushing to Factory

_nobody_ wrote over 2 years ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote over 2 years ago

@ryanbach Already checked in ... :-)

_nobody_ wrote over 2 years ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote over 2 years ago

done. :-)

_nobody_ wrote almost 2 years ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote almost 2 years ago

Thanks. Sounds good! An appropriate submitrequest would be appreciated and accepted. ;-)

akilgus wrote almost 2 years ago

Is the current (2020-01-09) state of Mesa in this repo supposed to work? There's a mixture of 19.3.1 (e.g. Mesa) and 19.2.6 (e.g. Mesa-dri) packages online - I had to go back to Leap 15.1's Mesa 18.3.2 to get the GUI up and running …

sndirsch wrote almost 2 years ago

Thanks. Indeed build of Mesa-driver on Leap 15.1/15.2 fails due to llvm version < 8. I'm trying to build llvm8 for Leap 15.1/15.2. Will take some time though ...

---

akilgus wrote almost 2 years ago

No need to hurry (at least not because of me). Just wanted to know if I broke something on my side or if the repo's the one to blame … ;)

---

sndirsch wrote almost 2 years ago

It has been the Mesa update to 19.3.1 .... which now needs llvm 8 ...

---

sndirsch wrote almost 2 years ago

@akilgus Meanwhile build against Leap 15.0/15.1 fixed. :-)

---

akilgus wrote almost 2 years ago

Thanks for your work. I'll give the new packages a try within the coming days.

_nobody_ wrote over 1 year ago

This comment has been deleted

• Delete comment?

  Please confirm deletion of comment

  Cancel
  Delete

sndirsch wrote over 1 year ago

Already on my TODO list. ;-)

zakhrov wrote about 1 year ago

Can we enable the MESA_VK_DEVICE_SELECT layer and the Mesa Vulkan Overlay layer for the Tumbleweed package?

sndirsch wrote about 1 year ago

Hmm. Could you come up with a concrete proposal for the package, preferrably a submit request? My guess is that I need to add -Dvulkan-device-select-layer=true as option for meson in specfile, but since you're apparently an expert here, it would be good if you could come up with something well tested.

---

zakhrov wrote about 1 year ago

I have branched the package and tried out some changes. They are in my obs repository here: https://build.opensuse.org/package/show/home:zakhrov:Mesa/Mesa It adds 2 packages. Mesa-vulkan-overlay and Mesa-vulkan-device-select which has the libraries and JSON files

---

zakhrov wrote about 1 year ago

I have submitted a request for it

ukbeast89 wrote 7 months ago

I've tried updating to 21.0.1. meson.build:21:0: ERROR: Value classic is not boolean (true or false)

sndirsch wrote 7 months ago

Valid values for -Dosmesa have changed. And a lot more. Mesa update won't be trivial this time. I tried for about two hours, but gave up then. May take several days to update Mesa this time. :-(

---

ukbeast89 wrote 6 months ago

-Dosmesa=classic \ is no longer being used. Removed that option and now notice ERROR: Options "swrast" are not in allowed choices: "auto, i915, i965, r100, r200, nouveau"

Looks like mesa has removed it https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST

sp1rit wrote 4 months ago

n_drirc-disable-rgb10-for-chromium-on-amd.patch is unneeded as it got fixed in gstreamer a few months ago:

https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/-/merge_requests/410

sndirsch wrote 4 months ago

Thanks. Done. See my latest changelog entry for Mesa sources.

BehzadA wrote 3 months ago

The Crocus driver(Intel 965G(Gen4)-Haswell(Gen7.5 and also Cherryview) Gallium-based driver) has been forgotten in the Spec files.

//-----------------------------------------

%ifarch %{ix86} x86_64

-Ddri-drivers=i915,i965,nouveau,r100,r200 \

-Dgallium-drivers=r300,r600,radeonsi,nouveau,swrast,svga,virgl,iris,crocus \

//------------------------------------------

Currently, the Crocus isn't enabled by default in Mesa 21.2

//------------------------------------------

mesa/meson_options.txt

option( 'prefer-crocus', type : 'boolean', value : false, description : 'Prefer new crocus driver over older i965 driver for gen4-7' )

//---------------------------------------

And users who want to use the Crocus driver should set the 'MESA_LOADER_DRIVER_OVERRIDE=crocus' environment variable, And if there is a problem with video hardware acceleration(vaapi driver), Should set the 'LIBVA_DRIVER_NAME=i965'

sndirsch wrote 3 months ago

Enabled. But currently build on %ix86 fails. This is the bigger issue right now.

---

BehzadA wrote 3 months ago

Thanks

I'm not a Mesa contributor, But I took a quick look and personally suspected GCC11.x(This is just a guess) because build with GCC7.x is successful(Leap_15.2 Mesa) but fails with GCC11.x, And also I remembered some opened issues on Mesa Gitlab that seems to be related to the GCC11

https://gitlab.freedesktop.org/mesa/mesa/-/issues/5069 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5067 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5068

---

sndirsch wrote 3 months ago

Thanks. I'm just wondering why Mesa 21.1.6 can still be built on %ix86 with GCC11 in place. So it needs to be related to changes in Mesa 21.2.0.

---

BehzadA wrote 2 months ago

The issue seems to be solved; Please checks Spec and conf files in my branch. https://build.opensuse.org/package/show/home:BehzadA:branches:X11:XOrg/Mesa Based on https://build.opensuse.org/package/show/home:tobijk:X11:XOrg:Unstable/Mesa Modified by me and need to be reviewed and also "Mesa-dri-kmsro" build is enabled.

---

sndirsch wrote 2 months ago

Thanks! I've fixed the build against %ix86 now by removing "-flto=auto" from cpp flags.