SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that may be so but i also like to get things working properly not only for me but others. I can still play d2 res on plain wine in its own prefix or on win10 vm, or on slackware-current
flawlessly if i want, lol.
I never said conty.sh couldn't get things working properly, merely that "i also like to get things working properly not only for me but others". It's nothing personal but i would like
to get slackware to do it with the right libraries and also i am already using lutris which up until recently has been doing great. Probably lutris updated its runtime librarys which would explain
why it runs flawlessly on slackware current. Perhaps slackwares' next release (like that comes very often) will correct the problem and until then we do what we can with what we have which tends
to quite stable as a result of not using rolling releases.
I thought that behavior changed around the time of the pre-Slackware 15 development cycle, about 2019?
More or less, there's a possibility it might happen, but you trust it will not happen again.
With a separate build machine, virtual or otherwise, possibility is not there and you know it will not happen again.
@ mickski56 are you sure that is all you did, i just looked and it is the same as my current slackbuild ?
I also um commented line 359:
# zcat $CWD/VulkanTools-sdk.gcc12.diff.gz | patch -p1 --verbose || exit 1
or did you keep it ?
My mistake, I've just run diff on the two slackbuilds. It was in there already and yes I did comment out gcc12 patch. I'm at a loss to offer anything further. Sorry.
well it looks like installing the vulkan sdk 1.3 in slackware 15 is the best solution to the problem. Running slackware current works but it still has problems so i would
wait for a newer more stable release for it to be a solution to getting vulkan 1.3 to be able to run diablo II resurrected on lutris. And no you do not need 32 bit vulkan
to run it. Yes you can run d2 res directly on wine but i had graphics problems that were more easily solved using lutris and dlss.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.