(old)Puppy Linux Discussion Forum

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

[wine-4.13 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.13_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.

davids45 wrote:G'day version2013,

I have not had any luck with your Wine64-4.xx pet. It installs from the pet and will "winecfg" in a terminal.
Notepad will then open but no other in-built windows application starts (e.g. winemine).
Trying to install a Windows-based application program also gets no response.

I appreciate your stated problem with 64-bit testing on your machine, but can you get, say, winemine, running as a test? I see its .exe file in two sub-directories in windows, system32 and systemwow64. I don't know which is more likely to work.

David S.

I installed wine64-4.13_v4.1.pet into the puppy distro: tahr64-6.0.5.

(creates a 64bit prefix)
# WINEPREFIX=/mnt/home/temp/wine winecfg

# WINEPREFIX=/mnt/home/temp/wine wine notepad
# WINEPREFIX=/mnt/home/temp/wine wine64 notepad

# WINEPREFIX=/mnt/home/temp/wine wine winemine
# WINEPREFIX=/mnt/home/temp/wine wine64 winemine


(creates a 32bit prefix) wiki
# WINEARCH=win32 WINEPREFIX=/mnt/home/temp/wine32 winecfg

# WINEPREFIX=/mnt/home/temp/wine32 wine notepad
# WINEPREFIX=/mnt/home/temp/wine32 wine winemine

All commands above appear to function as expected.

As expected, this fails to function:
# WINEPREFIX=/mnt/home/temp/wine32 wine64 winemine

I am unsure exactly why your wine install is problematic.

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

[wine-4.13 mirrors]

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

hi version2013 .
I was testing on dpupbuster 64 and it works very well.
They will only need 32-bit libraries.

32bit_compatibilty_dpupbuster64

you must change the MIME-types .

the new puppy is in in root there is now a symbolic link from the MIME-types folder
and with its package it cancels the link, and the other MIME-type stops working.
I would advise that the application_x-ms-dos-executable script, ,
created by a pinstall.sh with that it would not delete the folder, and it would work on all puppies.

Something like this .

josejp2424 wrote:you must change the MIME-types

Code: Select all

 /root/Choices/MIME-types/application_x-ms-dos-executable

.

the new puppy is in

Code: Select all

/etc/xdg/rox.sourceforge.net/MIME-types

in root there is now a symbolic link from the MIME-types folder
and with its package it cancels the link, and the other MIME-type stops working.
I would advise that the application_x-ms-dos-executable script, ,
created by a pinstall.sh with that it would not delete the folder, and it would work on all puppies.

Something like this .

Code: Select all

#!/bin/sh
echo "#!/bin/sh
exec wine "$@"
" >/root/Choices/MIME-types/application_x-ms-dos-executable && chmod +x /root/Choices/MIME-types/application_x-ms-dos-executable &

Interesting that there are multiples locations MIME-types can be found in puppies:
/root/Choices/MIME-types/
/root/.config/rox.sourceforge.net/MIME-types/
/etc/xdg/rox.sourceforge.net/MIME-types/

In the few puppy distros I have looked in, these locations appear to be present in all of the them.

I thought the default behavior for installing/copying files would be to follow the symlinks, not overwrite them.

In future wine compiles, I can put the file 'application_x-ms-dos-executable' in /etc/xdg/rox.sourceforge.net/MIME-types/

My attempt at compiling wine-4.14

[wine-4.14 mirrors]

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

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

wine_DOC-4.14.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.14/
> _____wine-4.14_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.14 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.14_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.

My attempt at compiling wine-4.15

[wine-4.15 mirrors]

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

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

wine_DOC-4.15.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.15/
> _____wine-4.15_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.15 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.15_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.

My attempt at compiling wine-4.16

[wine-4.16 mirrors]

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

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

wine_DOC-4.16.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.16/
> _____wine-4.16_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.16 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.16_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.

My attempt at compiling wine-4.17

[wine-4.17 mirrors]

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

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

wine_DOC-4.17.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.17/
> _____wine-4.17_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.17 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.17_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.

My attempt at compiling wine-4.18

[wine-4.18 mirrors]

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

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

wine_DOC-4.18.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.18/
> _____wine-4.18_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.18 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.18_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.

I was able to use this audio player when using WINE
https://mpesch3.de/1by1.html
___________________________________________________

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

My attempt at compiling wine-4.20

[wine-4.20 mirrors]

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

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

wine_DOC-4.20.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.20/
> _____wine-4.20_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 v3.2 ----------------------------------------------------------------------------------------------------------

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.

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

[wine-4.20 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used: https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.20_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.

My attempt at compiling wine-4.0.3

[wine-4.0.3 mirrors]

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

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

wine_DOC-4.0.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.0.3/
> _____wine-4.0.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]

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

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

------------
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 v2.2 ----------------------------------------------------------------------------------------------------------

----------------------------
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 v3.2 ----------------------------------------------------------------------------------------------------------

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.