Wine - run Windows programs in Linux

Virtual machines, emulation, etc.
Message
Author
User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#331 Post by Burn_IT »

WHY?????
"Just think of it as leaving early to avoid the rush" - T Pratchett

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#332 Post by bigpup »

version2013 wrote:I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
Do you have a 64bit processor, so the computer can run 64bit OS?

Do you need a new graphics card?
I have a few old Nvidia cards.
They work. I just upgraded over the years, so have some extra.
I could send you one.
No charge.
What you do for Puppy and Wine, needs to be rewarded!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#333 Post by bigpup »

Bionicpup64 7.9.6

Installed 'Wine64-3.0.3_v4.1.pet'
Installed 'wine_extras-v2.1.pet'

A lot of the Menu>Utility entries for Wine did not work.
Loaded the 32bit compatibility.sfs for Bionicpup64.
All the menu Wine entries now work.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

#334 Post by version2013 »

bigpup wrote: Do you have a 64bit processor, so the computer can run 64bit OS?
One of my computers is a 64-bit laptop with an AMD APU.
I want to learn to compile Mesa so I can have an updated graphics driver to test with on tahr64.

https://www.gamingonlinux.com/wiki/Buil ... rom_source

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-3.21

#335 Post by version2013 »

My attempt at compiling wine-3.21

[wine-3.21 mirrors]

wine-3.21_v1.1.pet _________ puppy 431 [stripped=true]
wine-3.21_v1.2.pet _________ puppy 431 [stripped=false]
wine_DEV-3.21_v1.1.pet ____ puppy 431
wine_DEV-3.21_v1.2.pet ____ puppy 431

wine-3.21_v2.1.pet _________ racy 5.5 [stripped=true]
wine-3.21_v2.2.pet _________ racy 5.5 [stripped=false]
wine_DEV-3.21_v2.1.pet ____ racy 5.5
wine_DEV-3.21_v2.2.pet ____ racy 5.5

wine-3.21_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-3.21_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-3.21_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-3.21_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-3.21.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/3.21/
> _____wine-3.21_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------
puppy 431
----------------

I compiled using puplet: Puppies 4.31.1 by forum member 'ttuuxxx'

mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso
mirrors | /distro/4.3__1/devx_430.sfs

This puplet uses glibc 2.6.1
The Wine files listing 'puppy 431' will possibly:
- fail with a glibc before 2.6.1
- succeed with a glibc of 2.6.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.7.1/fontconfig-2.7.1-i486-pup4.pet
fontconfig/2.7.1/fontconfig_DEV-2.7.1-i486-pup4.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libgphoto2/2.5.0/libgphoto2-2.5.0-i486_v2.pet
libgphoto2/2.5.0/libgphoto2_DEV-2.5.0-i486.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
libusb/1.0.9/libusb-1.0.9-i486_v2.pet
libusb/1.0.9/libusb_DEV-1.0.9-i486_v2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

[mirrors]
xorg/7.3/xorg_xorg_full_dri-7.3.pet
xorg/7.3/xorg_xorg_full_dri_DEV-7.3.pet

------------------------------------

When compiling in puppy 431, I used:
v1.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v1.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

------------
racy 5.5
------------

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.8.0/fontconfig-2.8.0-w5c.pet
fontconfig/2.8.0/fontconfig_DEV-2.8.0-w5c.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

----------------------------------------

When compiling in racy 5.5, I used:
v2.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v2.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-3.21

#336 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-3.21 mirrors]

wine64-3.21_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-3.21.pet __________ tahrpup64 6.0.5
wine64_DOC-3.21.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-3.21_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-3.0.4

#337 Post by version2013 »

My attempt at compiling wine-3.0.4

[wine-3.0.4 mirrors]

wine-3.0.4_v1.1.pet _________ puppy 431 [stripped=true]
wine-3.0.4_v1.2.pet _________ puppy 431 [stripped=false]
wine_DEV-3.0.4_v1.1.pet ____ puppy 431
wine_DEV-3.0.4_v1.2.pet ____ puppy 431

wine-3.0.4_v2.1.pet _________ racy 5.5 [stripped=true]
wine-3.0.4_v2.2.pet _________ racy 5.5 [stripped=false]
wine_DEV-3.0.4_v2.1.pet ____ racy 5.5
wine_DEV-3.0.4_v2.2.pet ____ racy 5.5

wine-3.0.4_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-3.0.4_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-3.0.4_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-3.0.4_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-3.0.4.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/3.0.4/
> _____wine-3.0.4_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------
puppy 431
----------------

I compiled using puplet: Puppies 4.31.1 by forum member 'ttuuxxx'

mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso
mirrors | /distro/4.3__1/devx_430.sfs

This puplet uses glibc 2.6.1
The Wine files listing 'puppy 431' will possibly:
- fail with a glibc before 2.6.1
- succeed with a glibc of 2.6.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.7.1/fontconfig-2.7.1-i486-pup4.pet
fontconfig/2.7.1/fontconfig_DEV-2.7.1-i486-pup4.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libgphoto2/2.5.0/libgphoto2-2.5.0-i486_v2.pet
libgphoto2/2.5.0/libgphoto2_DEV-2.5.0-i486.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
libusb/1.0.9/libusb-1.0.9-i486_v2.pet
libusb/1.0.9/libusb_DEV-1.0.9-i486_v2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

[mirrors]
xorg/7.3/xorg_xorg_full_dri-7.3.pet
xorg/7.3/xorg_xorg_full_dri_DEV-7.3.pet

------------------------------------

When compiling in puppy 431, I used:
v1.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v1.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

------------
racy 5.5
------------

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.8.0/fontconfig-2.8.0-w5c.pet
fontconfig/2.8.0/fontconfig_DEV-2.8.0-w5c.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

----------------------------------------

When compiling in racy 5.5, I used:
v2.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v2.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Last edited by version2013 on Sat 15 Dec 2018, 01:16, edited 1 time in total.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-3.0.4

#338 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-3.0.4 mirrors]

wine64-3.0.4_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-3.0.4.pet __________ tahrpup64 6.0.5
wine64_DOC-3.0.4.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-3.0.4_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-4.0

#339 Post by version2013 »

My attempt at compiling wine-4.0

[wine-4.0 mirrors]

wine-4.0_v1.1.pet _________ puppy 431 [stripped=true]
wine-4.0_v1.2.pet _________ puppy 431 [stripped=false]
wine_DEV-4.0_v1.1.pet ____ puppy 431
wine_DEV-4.0_v1.2.pet ____ puppy 431

wine-4.0_v2.1.pet _________ racy 5.5 [stripped=true]
wine-4.0_v2.2.pet _________ racy 5.5 [stripped=false]
wine_DEV-4.0_v2.1.pet ____ racy 5.5
wine_DEV-4.0_v2.2.pet ____ racy 5.5

wine-4.0_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.0_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.0_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.0_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.0.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.0/
> _____wine-4.0_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------
puppy 431
----------------

I compiled using puplet: Puppies 4.31.1 by forum member 'ttuuxxx'

mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso
mirrors | /distro/4.3__1/devx_430.sfs

This puplet uses glibc 2.6.1
The Wine files listing 'puppy 431' will possibly:
- fail with a glibc before 2.6.1
- succeed with a glibc of 2.6.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.7.1/fontconfig-2.7.1-i486-pup4.pet
fontconfig/2.7.1/fontconfig_DEV-2.7.1-i486-pup4.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libgphoto2/2.5.0/libgphoto2-2.5.0-i486_v2.pet
libgphoto2/2.5.0/libgphoto2_DEV-2.5.0-i486.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
libusb/1.0.9/libusb-1.0.9-i486_v2.pet
libusb/1.0.9/libusb_DEV-1.0.9-i486_v2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

[mirrors]
xorg/7.3/xorg_xorg_full_dri-7.3.pet
xorg/7.3/xorg_xorg_full_dri_DEV-7.3.pet

------------------------------------

When compiling in puppy 431, I used:
v1.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v1.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

------------
racy 5.5
------------

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages, as one sfs file, before compiling;
also known as dependencies:

[mirrors]
fontconfig/2.8.0/fontconfig-2.8.0-w5c.pet
fontconfig/2.8.0/fontconfig_DEV-2.8.0-w5c.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

----------------------------------------

When compiling in racy 5.5, I used:
v2.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v2.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Last edited by version2013 on Mon 11 Feb 2019, 23:03, edited 2 times in total.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-4.0

#340 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.0 mirrors]

wine64-4.0_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.0.pet __________ tahrpup64 6.0.5
wine64_DOC-4.0.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.0_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#341 Post by don570 »

I have noticed something strange so I will report...

I use wine64-3.17_v4.1.pet converted to SFS file for fatdog64 710

I load wine with load_SFS and then mount to view.

If I launch in terminal with command

Code: Select all

 ./wine64 
then mp3DirectCut will be slow

whereas if I launch with command...

Code: Select all

./wine
then mp3DirectCut plays the mp3 file fine.

_______________________________________

Maybe 64 bit emulation has bug with playing mp3 files with 32 bit program???

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-4.1

#342 Post by version2013 »

My attempt at compiling wine-4.1

[wine-4.1 mirrors]

* 1.x and 2.x failed to compile because of a bug.

wine-4.1_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.1_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.1_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.1_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.1.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.1/
> _____wine-4.1_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Last edited by version2013 on Wed 20 Feb 2019, 04:52, edited 3 times in total.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-4.1

#343 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.1 mirrors]

wine64-4.1_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.1.pet __________ tahrpup64 6.0.5
wine64_DOC-4.1.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.1_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

#344 Post by version2013 »

don570 wrote:I have noticed something strange so I will report...

I use wine64-3.17_v4.1.pet converted to SFS file for fatdog64 710

I load wine with load_SFS and then mount to view.

If I launch in terminal with command

Code: Select all

 ./wine64 
then mp3DirectCut will be slow

whereas if I launch with command...

Code: Select all

./wine
then mp3DirectCut plays the mp3 file fine.

_______________________________________

Maybe 64 bit emulation has bug with playing mp3 files with 32 bit program???
Testing a little differently.
I used Tahr64-6.0.5
I installed wine64-3.17_v4.1.pet (as a .pet file does)

Downloaded mp3DC225.exe and mpglibdll092.zip
from http://mpesch3.de1.cc/mp3dc.html

Installing and launching mp3Directcut with 'wine64', created a new 64bit ~/.wine prefix. It appeared to play a couple mp3 files as expected.

Deleted ~/.wine prefix.

Installing and launching mp3Directcut with 'wine', created a new 32bit .wine prefix. It appeared to play a couple mp3 files as expected.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-4.2

#345 Post by version2013 »

My attempt at compiling wine-4.2

[wine-4.2 mirrors]

* 1.x and 2.x failed to compile because of a bug.

wine-4.2_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.2_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.2_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.2_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.2.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.2/
> _____wine-4.2_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Last edited by version2013 on Wed 20 Feb 2019, 04:55, edited 2 times in total.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-4.2

#346 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.2 mirrors]

wine64-4.2_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.2.pet __________ tahrpup64 6.0.5
wine64_DOC-4.2.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.2_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine-4.3

#347 Post by version2013 »

My attempt at compiling wine-4.3

[wine-4.3 mirrors]

* 1.x and 2.x failed to compile because of a bug.

wine-4.3_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.3_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.3_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.3_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.3.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.3/
> _____wine-4.3_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post | page]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I compiled using tahrpup 6.0.5 PAE

mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso
mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup 6.0.5 PAE' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
I installed the following packages before compiling;
also known as dependencies:

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"
v3.2

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"
----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post | page] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Last edited by version2013 on Tue 12 Mar 2019, 15:46, edited 1 time in total.

version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:

Wine64-4.3

#348 Post by version2013 »

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.3 mirrors]

wine64-4.3_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.3.pet __________ tahrpup64 6.0.5
wine64_DOC-4.3.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

Code: Select all

ldd --version

Code: Select all

/lib/libc.so.6

Code: Select all

getconf GNU_LIBC_VERSION
----------------------------------------

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"
https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.3_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Last edited by version2013 on Tue 12 Mar 2019, 15:56, edited 1 time in total.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#349 Post by Burn_IT »

Join the queue!!!
"Just think of it as leaving early to avoid the rush" - T Pratchett

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#350 Post by Burn_IT »

Join the queue!!!
I don't have a comment, but I'll make a reply so that I can try to kid people I thought of something before they did.


Does the rule still apply that once someone has replied to a thread, edits are disallowed.
IT SHOULD DO.
"Just think of it as leaving early to avoid the rush" - T Pratchett

Post Reply