Not sure how this is supposed to work:
- So, wine in the repos is built with debugging symbols stripped, right?
- And there is no extra package like the "wine-dbg" like some ditros offer?
- I need wine with debug symbols though to submit (meaningful) bug reports to winehq I guess?
- To build wine, I need mesa libgl etc which conflicts with nvidia libgl
So, what's the right thing to do here if I need debug symbols?
Putting !strip into makepkg options
Doing a dirty remove (pacman -Rdd) + install to temporarily replace nvidia with mesa (which temporarily breaks just about everything - or at least it would if I'd accidentally reboot before undoing the changes)
... is what I'm doing at the moment. That doesn't really seem right though. Or is it?
Last edited by whoops (2013-07-30 16:49:29)
try building in a chroot, see https://wiki.archlinux.org/index.php/De … ean_Chroot
Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them
One one side that looks more complicated (+ like more work) then what I've been doing...
On the other side that looks a lot less "wrong"...
Not sure which one's better for me, need to try the chroot the next few times wine is updated I guess to figure that out.
Once you do it, it's actually very, very easy. A single command (extra-<arch>-build) sets up the chroot or cleans and updates it if it already exists, installs deps and makedeps, and builds the package.
The mesa-libgl package doesn't contain any headers or other dev stuff, so I don't know why wine has it in makedepends. Just remove mesa-libgl from the wine PKGBUILD, see if it builds. In theory, it should.
If it needs to link to libGL.so.*, the file kind of needs to be there.
Nvidia provides a libGL.so. Other packages makedepend on libgl, which can be provided by either mesa-libgl or nvidia-libgl.
Oh... hmm... right, I never really understood why it needs mesa-libgl instead of nvidia-libgl (which provides libgl / libgl.so.*)... no idea why I never got around to just *try* - definitely should have...
Anyway: test build just finished. wine seems to build fine with nvidia-libgl and the windows application I ran after that had no problems. Great, that solves this problem!
Does that sound like submission as a bug is justified?
I'm not sure what's the bug though - if there is one.
Should libgl (+lib32) not be a build dependency of wine?
Or should makepkg recognize that nvidia-libgl provides libgl and accept that instead?
Last edited by whoops (2013-07-30 16:50:25)
What other packages? AFAIK, no packages in the main repos are set up like that, and they shouldn't be since a virtual dep as a makedep doesn't make much sense. PKGBUILDs in the main repos are specifically set up to be built in a chroot with devtools, since that's how every binary package in the official repos is built.
Go to the mesa-libgl page, check the "Required by" column for "(requires libgl) (make)". Those other packages. Then there's a lot packages that don't list libgl (any kind of libgl) in makedepends at all, they only have libgl in depends. It doesn't seem to be a problem for devtools. Not sure how exactly devtools deals with this, but if I were to guess, it simply automatically grabs the first libgl provider.
Last edited by Gusar (2013-07-30 17:12:08)