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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
andrew.46 I have found that the guys in #winehackers on freenode are pretty excited when you can articulate a bug for them to fix. They seek them out... Have you tried talking to them directly?
andrew.46 I have found that the guys in #winehackers on freenode are pretty excited when you can articulate a bug for them to fix. They seek them out... Have you tried talking to them directly?
I confess that I have not. A quick google suggests that this is an issue that has been around since 2007 with variations of the work-around that has been suggested on this thread. So a 12 year old issue? Looks like the original bug is here and you can see that it is marked as 'Not a Wine bug'.
all I can do is hope AlienBOB makes a pass over it with his magic, multilib and staging...
You can build it yourself, here's the patch for his wine.SlackBuild for wine 4.0, note the part about gallium-nine being stripped out since it's an standalone project now. https://github.com/iXit/wine-nine-standalone
Code:
--- wine.SlackBuild.orig 2019-01-07 19:26:57.471986742 +0100
+++ wine.SlackBuild 2019-02-03 11:34:27.334078489 +0100
@@ -118,6 +118,10 @@
# * Update.
# 2.21-1 28/dec/2017 by Eric Hameleers <alien@slackware.com>
# * Update.
+# 4.0 3/feb/2019
+# * Removed d3d9 since gallium-nine is an standalone project now.
+# https://github.com/iXit/wine-nine-standalone/releases/
+# updated staging link https://github.com/wine-staging/wine-staging/
#
# Run 'sh wine.SlackBuild' to build a Slackware package.
# The package (.txz) plus descriptive .txt file are created in /tmp .
@@ -127,7 +131,7 @@
PRGNAM=wine
-SRCVER=${SRCVER:-"2.21"}
+SRCVER=${SRCVER:-"4.0"}
VERSION=$(echo $SRCVER | tr '-' '.')
BUILD=${BUILD:-1}
TAG=${TAG:-alien}
@@ -135,14 +139,6 @@
# If you do not want wine64 on Slackware64, set this to "no":
DO_WINE64=${DO_WINE64:-"yes"}
-## Slackware until 14.1 does not have d3dadapter aka "nine" ebabled in mesa:
-if /usr/bin/pkg-config --exists d3d ; then
- echo "-- Adding d3dadapter"
- USE_NINE=${USE_NINE:-"YES"}
-else
- USE_NINE=${USE_NINE:-"NO"}
-fi
-
# Add the "Gecko", Wine's own implementation of Internet Explorer.
# For matching wine_gecko & wine versions, see http://wiki.winehq.org/Gecko
GECKO=${GECKO:-2.47}
@@ -154,7 +150,7 @@
# In a 64 bit wineprefix, substitute wine64 for wine in the above command.
# If you do not want to add mono, define MONO=NO instead of a number.
# See https://wiki.winehq.org/Mono
-MONO=${MONO:-4.7.1}
+MONO=${MONO:-4.7.5}
DOCS="ANNOUNCE AUTHORS COPYING.LIB ChangeLog LICENSE* README VERSION"
@@ -212,16 +208,9 @@
DLI=$(($DLI+1))
SOURCE[$DLI]="$SRCDIR/${PRGNAM}-staging-${SRCVER}.tar.gz"
-SRCURL[$DLI]="https://github.com/${PRGNAM}-compholio/${PRGNAM}-staging/archive/v${SRCVER}.tar.gz"
+SRCURL[$DLI]="https://github.com/${PRGNAM}-staging/${PRGNAM}-staging/archive/v${SRCVER}.tar.gz"
STAGINGSRC="${SOURCE[$DLI]}"
-if [ "$USE_NINE" = "YES" ]; then
- DLI=$(($DLI+1))
- SOURCE[$DLI]="$SRCDIR/${PRGNAM}-d3d9-${SRCVER}.tar.gz"
- SRCURL[$DLI]="https://github.com/sarnex/wine-d3d9-patches/archive/${PRGNAM}-d3d9-${SRCVER}.tar.gz"
- NINESRC="${SOURCE[$DLI]}"
-fi
-
DLI=$(($DLI+1))
SOURCE[$DLI]="$SRCDIR/wine_gecko-${GECKO}-x86.msi"
SRCURL[$DLI]="http://dl.winehq.org/wine/wine-gecko/${GECKO}/wine_gecko-${GECKO}-x86.msi"
@@ -332,15 +321,6 @@
tar -xf ${STAGINGSRC} --strip-components 1
./patches/patchinstall.sh DESTDIR="$(pwd)" --all \
2>&1 | tee -a $OUTPUT/patch-${PRGNAM}.log
-if [ "$USE_NINE" = "YES" ]; then
- # Apply the Direct3D9 patch set:
- echo -e "\n**\n** direct3d9:\n**" | tee -a $OUTPUT/patch-${PRGNAM}.log
- tar xvf ${NINESRC} --strip-components 1
- cat staging-helper.patch | patch -p1 --verbose \
- 2>&1 | tee -a $OUTPUT/patch-${PRGNAM}.log
- cat wine-d3d9.patch | patch -p1 --verbose \
- 2>&1 | tee -a $OUTPUT/patch-${PRGNAM}.log
-fi
chown -R root:root .
chmod -R u+w,go+r-w,a+X-s .
@@ -357,12 +337,6 @@
DO_GL="--without-opengl"
fi
-if [ "$USE_NINE" = "YES" -o "$USE_NINE" = "yes" ]; then
- DO_NINE="--with-d3d9-nine"
-else
- DO_NINE=""
-fi
-
export CCAS="as"
export CFLAGS="$SLKCFLAGS"
export CXXFLAGS="$SLKCFLAGS"
@@ -381,7 +355,6 @@
--mandir=/usr/man \
--with-x \
${DO_GL} \
- ${DO_NINE} \
--program-prefix= \
--program-suffix= \
--build=$TARGET \
Yeah I have issues with 32bit Slackware 14.2, the build stalls on the compilation of dlls/ntdlls/server.c. The packages for 32bit -current and for all 64bit variants compile just fine.
The SlackBuild script on SBo for wine-4.0 has a workaround for this apparently but it does not work for me.
I'll try fixing the 32bit Slackware 14.2 build first, before uploading new packages.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 413
Rep:
Quote:
Originally Posted by Alien Bob
...I'll try fixing the 32bit Slackware 14.2 build...
And he did. Packages for -current and 14.2, both 32 and 64bit, in AlienBobs repo since yesterday afternoon! Please note what he writes in the changelog about the OpenAL dependency.
On a slackware64-current do I need multilib installed for running wine-4.0 compiled by Alien Bob.
Desktop manager is xfce-4.12
In a wine-4.0-x86_64-1alien.dep are listed only OpenAL and libva. Multilib is not mentioned.
wincfg returns:
Quote:
/usr/bin/winecfg: line 46: /usr/bin/wine: No such file or directory
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.