(old)Puppy Linux Discussion Forum

Posted: **Mon 09 Dec 2019, 03:52**

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

[wine-4.0.3 mirrors]

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

Posted: **Mon 16 Dec 2019, 16:25**

My attempt at compiling wine-4.21

[wine-4.21 mirrors]

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

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

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

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.

Posted: **Mon 16 Dec 2019, 16:26**

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

[wine-4.21 mirrors]

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

Posted: **Thu 19 Dec 2019, 17:26**

I discovered that KRITA 3.3 paint program(32bits) including gmic plugins can be run with Wine 4

https://download.kde.org/stable/krita/3 ... .3-x86.zip

__________________________________________________

Posted: **Thu 19 Dec 2019, 18:09**

@version2013 Thanks for

Code: Select all

root# wine --version
wine-4.21

Posted: **Thu 26 Dec 2019, 04:04**

My attempt at compiling wine-5.0-rc1

[wine-5.0-rc1 mirrors]

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

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

wine_DOC-5.0-rc1.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/5.0-rc1/
> _____wine-5.0-rc1_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.

Posted: **Thu 26 Dec 2019, 04:05**

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

[wine-5.0-rc1 mirrors]

wine64-5.0-rc1_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc1.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc1.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-5.0-rc1_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.

Posted: **Mon 30 Dec 2019, 01:06**

My attempt at compiling wine-5.0-rc2

[wine-5.0-rc2 mirrors]

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

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

wine_DOC-5.0-rc2.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/5.0-rc2/
> _____wine-5.0-rc2_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.

Posted: **Mon 30 Dec 2019, 01:07**

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

[wine-5.0-rc2 mirrors]

wine64-5.0-rc2_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc2.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc2.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-5.0-rc2_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.

Posted: **Mon 30 Dec 2019, 04:54**

version2013 wrote:My attempt at compiling wine-5.0-rc2

[wine-5.0-rc2 mirrors]

2.x failed to compile because of a bug

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

wine_DOC-5.0-rc2.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/5.0-rc2/
> _____wine-5.0-rc2_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.

Thank you very much for your work version2013. in Dpupbuster64 they work very well.

Posted: **Thu 02 Jan 2020, 03:35**

My attempt at compiling wine-5.0-rc3

[wine-5.0-rc3 mirrors]

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

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

wine_DOC-5.0-rc3.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/5.0-rc3/
> _____wine-5.0-rc3_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.

Posted: **Thu 02 Jan 2020, 03:36**

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

[wine-5.0-rc3 mirrors]

wine64-5.0-rc3_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc3.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc3.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-5.0-rc3_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.

Posted: **Thu 09 Jan 2020, 04:36**

My attempt at compiling wine-5.0-rc4

[wine-5.0-rc4 mirrors]

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

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

wine_DOC-5.0-rc4.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/5.0-rc4/
> _____wine-5.0-rc4_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.

Posted: **Thu 09 Jan 2020, 04:37**

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

[wine-5.0-rc4 mirrors]

wine64-5.0-rc4_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc4.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc4.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-5.0-rc4_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.

Posted: **Sat 11 Jan 2020, 19:15**

32 bit windows version of reaper (Digital Audio Workstation) ran well on wine
https://www.reaper.fm/download.php

To make the audio work I set reaper preferences as in image...
_____________________________________________

Posted: **Wed 15 Jan 2020, 01:11**

My attempt at compiling wine-5.0-rc5

[wine-5.0-rc5 mirrors]

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

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

wine_DOC-5.0-rc5.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/5.0-rc5/
> _____wine-5.0-rc5_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.

Posted: **Wed 15 Jan 2020, 01:12**

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

[wine-5.0-rc5 mirrors]

wine64-5.0-rc5_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc5.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc5.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-5.0-rc5_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.

Posted: **Fri 24 Jan 2020, 03:31**

My attempt at compiling wine-5.0-rc6

[wine-5.0-rc6 mirrors]

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

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

wine_DOC-5.0-rc6.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/5.0-rc6/
> _____wine-5.0-rc6_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.

Posted: **Fri 24 Jan 2020, 03:32**

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

[wine-5.0-rc6 mirrors]

wine64-5.0-rc6_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0-rc6.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0-rc6.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-5.0-rc6_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.

Posted: **Mon 27 Jan 2020, 02:53**

My attempt at compiling wine-5.0

[wine-5.0 mirrors]

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

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

wine_DOC-5.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/5.0/
> _____wine-5.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]

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.

(old)Puppy Linux Discussion Forum

Wine - run Windows programs in Linux

wine64-4.0.3

wine-4.21

wine64-4.21

wine-5.0-rc1

wine64-5.0-rc1

wine-5.0-rc2

wine64-5.0-rc2

Re: wine-5.0-rc2

wine-5.0-rc3

wine64-5.0-rc3

wine-5.0-rc4

wine64-5.0-rc4

wine-5.0-rc5

wine64-5.0-rc5

wine-5.0-rc6

wine64-5.0-rc6

wine-5.0