Wine - run Windows programs in Linux

Virtual machines, emulation, etc.
Post Reply
Message
Author
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.0

#421 Post by version2013 »

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

[wine-5.0 mirrors]

wine64-5.0_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-5.0.pet __________ tahrpup64 6.0.5
wine64_DOC-5.0.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_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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.1

#422 Post by version2013 »

My attempt at compiling wine-5.1

[wine-5.1 mirrors]

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

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

wine_DOC-5.1.pet

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

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

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

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.1

#423 Post by version2013 »

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

[wine-5.1 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.1_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Top
User avatar
Moose On The Loose
Posts: 965
Joined: Thu 24 Feb 2011, 14:54

Wine 5.1 on Precise-light

#424 Post by Moose On The Loose »

I have precise-light
Booted with no save file so it is as it came
installed the 5.1 pet
did the install of ExpressPCBPlus
Went to the directory on "C:" under wine
opened a terminal and ran the program

Code: Select all

# wine ExpressPCBPlus.exe
001d:err:module:load_so_dll failed to load .so lib "/usr/bin/../lib32/wine/winebus.sys.so": libudev.so.1: cannot open shared object file: No such file or directory
001d:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebus": c0000142
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1114
0009:err:module:load_so_dll failed to load .so lib "/usr/bin/../lib32/wine/l3codeca.acm.so": libmpg123.so.0: cannot open shared object file: No such file or directory
Failed to run module constructor due to (null) assembly:C:\windows\mono\mono-2.0\lib\mono\4.5\mscorlib.dll type:TypeInitializationException member:(null)
#
You can get the program from www.expresspcb.com if you want to try it in a different version.

Previously, I tried 3.1 is also didn't work. On it the "libmpg123" was missing. I compiled that lib and added it to the system and tried again with still no luck.

The program involved uses mono.
Back on 3.1, I had tested that non-mono programs worked
Top
User avatar
mikeslr
Posts: 3890
Joined: Mon 16 Jun 2008, 21:20
Location: 500 seconds from Sol

#425 Post by mikeslr »

ExpressPCBPlus is an enhanced version of ExpressPCB. The additions and changes are detailed here, https://www.expresspcb.com/expresspcb-2-0-whats-new/. WineHQ reports no successful use of ExpressPCBPlus under any version of Windows; only "ExpressPCB Plus 1.1 (.NET 3.5 SP1 app) throws 'System.NotImplementedException: Not implemented at System.Drawing.Pen.TranslateTransform' (GdipTranslatePenTransform not implemented)" https://www.winehq.org/announce/3.5. IIRC, .NET involves the "Mono" and may explain why moose-on-the-loose could successfully run the earlier version which did not require it.

ExpressPCB (Not Plus) received a gold rating. https://appdb.winehq.org/objectManager. ... n&iId=3903 but bears the following advice:

"For this app, using filemon.exe, ExpressPCB made an ouside "QUERY" to C:\Winnt or C:Windows \SYSTEM32\OLEAUT32.dll. In winecfg, goto .dll tab and "ADD" oleaut32.dll. Run from console #wine "C:\Program Files\ExpressPCB\ExpressSCH.exe". It should start and load libraries and then be ready for use. If you need to add this file, it is available for download. Just type in "oleaut32.dll" download - www.dll-files.com/dllindex/dll-files.shtml?oleaut32 - and install in the system32 directory. This .dll is the core of Microsoft's OLE technology. Let me know if you have any troubles".

Unless and until Wine Devs sort out the "NET/Mono" problem, I suggest trying to live with ExpressPCB.
Top
User avatar
Moose On The Loose
Posts: 965
Joined: Thu 24 Feb 2011, 14:54

#426 Post by Moose On The Loose »

mikeslr wrote:ExpressPCBPlus is an enhanced version of ExpressPCB.
[.. go back and read for more ....]
I am setting aside the ExpressPCBPlus issue for a few days.
I have discovered that the gcc in precise i not the latest and won't compile wine.
I also found that the dev stuff for precise also won't compile the new gcc.

The good news:
LTSpice works extremely well.
It is a full up electronic circuit simulation with some added features.
You get it from www.analog,com

Although it was created to sell Linear Technology parts it is not limited to them. Please don't use it to design ICs without asking them and perhaps giving them money for the right to do that.

It does "logic" or "digital" stuff in a straight forward way..

On puppy, you may want to direct the storage of the xxxx.raw file to be on a real (nonFAT) hard disk and not into the in memory storage. There are large files. There are huge files. There are really-really massive files and then there are the xxxx.raw files.
Top
User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#427 Post by bigpup »

Check the info on WineHQ for any program you try to run in Wine.
ExpressPCB
https://appdb.winehq.org/objectManager. ... n&iId=3903
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.2

#428 Post by version2013 »

My attempt at compiling wine-5.2

[wine-5.2 mirrors]

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

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

wine_DOC-5.2.pet

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

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

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

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.2

#429 Post by version2013 »

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

[wine-5.2 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.3

#430 Post by version2013 »

My attempt at compiling wine-5.3

[wine-5.3 mirrors]

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

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

wine_DOC-5.3.pet

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


experimental wine build:
wine-5.3_v3.3.pet _________ tahrpup 6.0.5 PAE [stripped=true]
[mirror]
configured to install in /opt/wine/ instead of /usr/

----------------------------------------------------------------
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.3/
> _____wine-5.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.

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

----------------------------
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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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"
v3.3

Code: Select all

configure --prefix=/opt/wine --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/opt/wine/lib32 CFLAGS="-O2 -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 Mon 09 Mar 2020, 21:46, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.3

#431 Post by version2013 »

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

[wine-5.3 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.4

#432 Post by version2013 »

My attempt at compiling wine-5.4

[wine-5.4 mirrors]

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

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.4

#433 Post by version2013 »

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

[wine-5.4 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.5

#434 Post by version2013 »

My attempt at compiling wine-5.5

[wine-5.5 mirrors]

2.x failed to compile because of a bug
With patch applied, compilation failed with bug 47907

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

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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 Thu 07 May 2020, 04:53, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.5

#435 Post by version2013 »

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

[wine-5.5 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.6

#436 Post by version2013 »

My attempt at compiling wine-5.6

[wine-5.6 mirrors]

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

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.6

#437 Post by version2013 »

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

[wine-5.6 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.7

#438 Post by version2013 »

My attempt at compiling wine-5.7

[wine-5.7 mirrors]

2.x failed to compile because of a bug
I am assuming bug 47907 still applies, just that bug 49106 caused crash first.

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

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

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

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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 Thu 07 May 2020, 05:03, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine64-5.7

#439 Post by version2013 »

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

[wine-5.7 mirrors]

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

----------------------------
tahrpup64 6.0.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.

Puppy Package Manager > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1
gcc-mingw-w64_4.8.2-10ubuntu2+12
gcc-mingw-w64-base_4.8.2-10ubuntu2+12
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12
mingw-w64_3.1.0-1
mingw-w64-common_3.1.0-1
mingw-w64-i686-dev_3.1.0-1
mingw-w64-x86-64-dev_3.1.0-1

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

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.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.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

wine-5.8

#440 Post by version2013 »

My attempt at compiling wine-5.8

[wine-5.8 mirrors]

2.x failed to compile because of a bug
I am assuming bug 47907 still applies, just that bug 49106 caused crash first.

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

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

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

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

----------------------------
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

Puppy Package Manager (update database) > mingw-w64_3.1.0-1
binutils-mingw-w64-i686_2.23.52.20130620-1ubuntu1+3build1_i386.deb
binutils-mingw-w64-x86-64_2.23.52.20130620-1ubuntu1+3build1_i386.deb
gcc-mingw-w64_4.8.2-10ubuntu2+12_all.deb
gcc-mingw-w64-base_4.8.2-10ubuntu2+12_i386.deb
gcc-mingw-w64-i686_4.8.2-10ubuntu2+12_i386.deb
gcc-mingw-w64-x86-64_4.8.2-10ubuntu2+12_i386.deb
g++-mingw-w64_4.8.2-10ubuntu2+12_all.deb
g++-mingw-w64-i686_4.8.2-10ubuntu2+12_i386.deb
g++-mingw-w64-x86-64_4.8.2-10ubuntu2+12_i386.deb
mingw-w64_3.1.0-1_all.deb
mingw-w64-common_3.1.0-1_all.deb
mingw-w64-i686-dev_3.1.0-1_all.deb
mingw-w64-x86-64-dev_3.1.0-1_all.deb

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

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 Fri 19 Jun 2020, 05:58, edited 1 time in total.
Top
Post Reply

Return to “Virtualization”