Wine - run Windows programs in Linux

Virtual machines, emulation, etc.
Message
Author
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

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

Wine-4.4

#351 Post by version2013 »

My attempt at compiling wine-4.4

[wine-4.4 mirrors]

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

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

wine_DOC-4.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/4.4/
> _____wine-4.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.

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

----------------------------
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 Sun 24 Mar 2019, 23:03, edited 3 times in total.

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

Wine64-4.4

#352 Post by version2013 »

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

[wine-4.4 mirrors]

wine64-4.4_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.4.pet __________ tahrpup64 6.0.5
wine64_DOC-4.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-4.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.5

#353 Post by version2013 »

My attempt at compiling wine-4.5

[wine-4.5 mirrors]

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

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

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

wine_DOC-4.5.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.5/
> _____wine-4.5_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 combined the following files into one .sfs, then loaded that file.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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 combined the following files into one .sfs, then loaded that file.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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 08 Apr 2019, 03:12, edited 2 times in total.

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

Wine64-4.5

#354 Post by version2013 »

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

[wine-4.5 mirrors]

wine64-4.5_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.5.pet __________ tahrpup64 6.0.5
wine64_DOC-4.5.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.5_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 Mon 08 Apr 2019, 00:05, edited 1 time in total.

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

#355 Post by Burn_IT »

Are you German by origin??
Slapping your towels on all the beach chairs??
"Just think of it as leaving early to avoid the rush" - T Pratchett

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

Wine-4.6

#356 Post by version2013 »

My attempt at compiling wine-4.6

[wine-4.6 mirrors]

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

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

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

wine_DOC-4.6.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.6/
> _____wine-4.6_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 files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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.2.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 files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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.2.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 files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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 24 Apr 2019, 02:08, edited 1 time in total.

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

Wine64-4.6

#357 Post by version2013 »

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

[wine-4.6 mirrors]

wine64-4.6_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.6.pet __________ tahrpup64 6.0.5
wine64_DOC-4.6.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.6_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.7

#358 Post by version2013 »

My attempt at compiling wine-4.7

[wine-4.7 mirrors]

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

wine_DOC-4.7.pet

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


wine-4.7 required bison version 3.0 or newer to compile.
Added bison files to the dependency list for puppy 431 and racy 5.5
Possibly only a build dependency and not required for general wine use.

wine failed to compile on puppy 431 and racy 5.5 because of an error.

Without doing a bisect to find the commit that caused the compile error, and based on the error message, here is my guess.
qcap: Use the v4l2 device_caps field if supported. [https://www.winehq.org/announce/4.7]
qcap: Use the v4l2 device_caps field if supported. [https://source.winehq.org/git/wine.git/ ... 95b2448da2]

Here is my guess as to the commit in wine-4.8 that fixed the issue.
qcap: Fix compilation with older videodev2.h. [https://source.winehq.org/git/wine.git/ ... 73d21ff2e0]

----------------------------------------------------------------
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.7/
> _____wine-4.7_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]

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

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

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

I installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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] 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 22 May 2019, 21:20, edited 8 times in total.

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

Wine64-4.7

#359 Post by version2013 »

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

[wine-4.7 mirrors]

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

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

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.7_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.8

#360 Post by version2013 »

My attempt at compiling wine-4.8

[wine-4.8 mirrors]

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

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

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

wine_DOC-4.8.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.8/
> _____wine-4.8_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]

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

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

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

I installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[mirrors]
bison/3.3/bison-3.3_v1.2.pet
bison/3.3/bison_DEV-3.3_v1.2.pet

[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.2.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 installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[mirrors]
bison/3.3/bison-3.3_v1.2.pet
bison/3.3/bison_DEV-3.3_v1.2.pet

[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.2.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 installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[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] 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-4.8

#361 Post by version2013 »

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

[wine-4.8 mirrors]

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

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

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.8_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.

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

Any success in running Excel in Wine

#362 Post by B.K. Johnson »

Hello Wine lovers
I am a Windows refugee of 10 years. I haven't used the OS in the decade although XP is still on my hard drive. I think I may need to do some Excel work so I am thinking of Excel running in Wine. If anyone has done so, I'd appreciate some help, your successes and failures before I bother to install Wine. A search for Excel in the thread turned up empty.

TIA
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#363 Post by Mike Walsh »

@ B.K.J:-

You won't find any mention of apps/programs in this thread; it's all about the WINE environment. To find out whether Windoze stuff will work with WINE, you need to consult the WINE HQ database. It's huge, comprising around 15,000 entries at present.....and it's growing, day by day.

The database can be found here:-

https://appdb.winehq.org/

To save you the trouble of trying to find it, here's the page for Excel:-

https://appdb.winehq.org/objectManager. ... ion&iId=11

The database exists due to user reviews of how well things perform under WINE, along with bug reports, ratings, etc. I myself submitted a review for Photoshop CS2 a couple of years back. Nothing is guaranteed with WINE; you can only try things out, and see what happens.

I have an elderly copy of Office 2000, donated by a friend, years ago, when I still used XP. Word works fine under WINE; I've never bothered with Excel, due to the fact that on the rare occasions I need a spreadsheet program, I use SoftMaker's FreeOffice. The 2018 version's spreadsheet is identical to Excel in every way that counts; it even looks the same.

Even different releases of Office will behave differently. TBH, since there's so many decent Linux alternatives around, I can't really see the need for using M$ Office under WINE. The current version of FreeOffice even gives you the option for the infamous 'ribbon' interface, should you desire it!

I only installed Word 2000 for the hell of it, to see what, if anything, would happen.....and was pleasantly surprised when it all functioned as it should. One tip, though; don't ever try to install Outlook; it'll bork things completely. There are certain things about Outlook that have only ever been produced by Microsoft, and WINE, so far, has never been able to emulate them; I think they mainly center around the way that Windows connects to the internet, and specifically the Outlook servers.

IF you're interested, you can find my packages for FreeOffice here:-

http://www.murga-linux.com/puppy/viewtopic.php?t=112318

Hope some of that helps.


Mike. :wink:

B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#364 Post by B.K. Johnson »

@Mike Walsh
Thanks Mike. Your post will certainly help.
Most times my spreadsheet needs are satisfied my gnumeric, and LibreOffice Calc but this time, I'll need the real deal. I feel sure I have Excel on my XP which I'll go to as a last resort. I am not in an immediate hurry anyway, but I'll check your kinks. Thanks again.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]

User avatar
mikeslr
Posts: 3890
Joined: Mon 16 Jun 2008, 21:20
Location: 500 seconds from Sol

Excel under Wine

#365 Post by mikeslr »

WineHQ reports the following about Excel, https://appdb.winehq.org/objectManager. ... ion&iId=11 with Platinum suggesting everything works, Gold almost everything, Silver --pretty much, and after that not worth the effort to install. Your experience may differ, depending on which versions of Excel and Wine you use. My experience is that the newer the version of Wine, the better.

But, like Mike Walsh, I have to wonder why you think you 'need the the real deal'. While building Slacko 5.7.2.CE, I explored various alternatives to gnumeric before deciding to leave it in. Although xls isn't gnumeric's native format, I discovered it could both read and wrote files with that format to the extent that I could download xls Templates and use them. One difference I noticed was how I had to write the Sum forumula. However, when an Excel template was loaded, gnumeric handled the difference internally.

As Mike Walsh said, FreeOffice is designed to be entirely compatible with microsoft's Excel. So, by the way is WPS Office.

Post Reply