Identifying Wine Dependencies

enorbet · 12-03-2015, 09:31 PM

Greetings
I am still running Slackware 14.0 32 bit (exactly because Wine is simpler with 32 bit and the performance hit in general is negligible) and have been running AlienBob's slackbuild for Wine but it is stuck at v 1.6. Latest Wine is up to 1.7.55 and it seems the major obstacle to upgrading is Glibc. However I can't seem to easily discover the cutoff point. How do I discover the latest Wine package that I can "upgradepkg" to that will be happy with Slack 14.0? especially Glibc version, which, iirc, is v 2.15 on Slack 14.0.

I'd like to set aside a whole day to upgrade first to 14.1, boot once, and then to 14.2 when it arrives. Until now the upgrades in 14.1 haven't been sufficiently compelling for me to change and I'd prefer to hold off a little longer if possible.

Any help appreciated.

elcore · 12-04-2015, 12:11 AM

For 14.0 you can either use the old package built for 14.0 or compile your own package, I don't think the one built for 14.1 will work there.
The wine package will generally depend on things it was compiled with, if some library changes version, wine probably needs rebuilding.
You can easily find the full list of these things inside tarball configure file, and then use the slackbuild to add/remove the opts you want.
It's a huge file so I won't paste it here, relevant options start at ac_user_opts
I can share my slackbuild config that compiles fast and works on 14.1 (version 1.7.54) but the result won't be any good if you require oss or cups for example.

Code:

# All of the libraries produced are 32bit libs anyway
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --mandir=/usr/man \
  --docdir=/usr/doc/$PRGNAM-$VERSION \
  --with-gnutls=yes      \
  --with-x               \
  --with-alsa            \
  --with-opengl          \
  --without-capi         \
  --without-cups         \
  --without-gsm          \
  --without-gphoto       \
  --without-hal          \
  --without-ldap         \
  --without-netapi       \
  --without-opencl       \
  --without-oss          \
  --without-pcap         \
  --without-sane         \
  --disable-tests        \
  --disable-wordpad      \
  --disable-winemine     \
  --disable-notepad      \
  --disable-iexplore     \
  --disable-documentation  \
  --build=$ARCH-slackware-linux

make depend
make
make install DESTDIR=$PKG

dugan · 12-04-2015, 12:47 AM

Just build your own.

enorbet · 12-04-2015, 12:46 PM

Sincere thanks to both elcore and dugan since both helped describe what I need to do. Dugan I have used your staging build in the past and very much liked the effect that has so I'm glad that is included in your build. Now I have work to do

Thanks again!

enorbet · 12-08-2015, 11:44 AM

Update Thanks again for the well-written scripts. My main box with 14.0 is now running Wine-1.8-rc2 flawlessly and with latest Winetricks as well. Proper job.

elcore · 12-09-2015, 02:07 AM

Forgot to mention there's a possible problem with libglx.so that links to nvidia driver instead of mesa.
From what I've read, one shouldn't distribute a wine package compiled with that driver because of the licence.

enorbet · 12-09-2015, 03:59 PM

I'm not sure I understand. I don't get it why people give nVidia a hard time about remaining proprietary. When the GPL was first conceived, from it's earliest beginnings, it was acknowledged and planned that some software, especially of the hardware-specific variety, could and should remain closed but coexist with FOSS. Even if you and others think nVidia is unjustifiably paranoid don't we have to admit that their business model works and provides those who choose to use their hardware with exceptionally high quality support, at no cost to us? Seems like a Win-Win to me.

dugan · 12-09-2015, 04:05 PM

Quote:

Originally Posted by elcore

Forgot to mention there's a possible problem with libglx.so that links to nvidia driver instead of mesa.
From what I've read, one shouldn't distribute a wine package compiled with that driver because of the licence.

1. Who said anything about distributing a Wine package?

2. Where did you read that?

elcore · 12-09-2015, 11:29 PM

Quote:

Originally Posted by dugan

1. Who said anything about distributing a Wine package?

2. Where did you read that?

There's a warning on Trinity site about packages compiled with-opengl, with that driver, shouldn't be distributed.
Just saying there's a possible problem, because it's well known that nvidia driver is replacing parts of mesa.
Not that I'm worried about it, I build it locally and I don't distribute.