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

#361 Post by version2013 »

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

[wine-4.8 mirrors]

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

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

When compiling in tahrpup64 6.0.5, I used:

Code: Select all

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

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Top
B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

Any success in running Excel in Wine

#362 Post by B.K. Johnson »

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

TIA
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
Top
User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#363 Post by Mike Walsh »

@ B.K.J:-

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

The database can be found here:-

https://appdb.winehq.org/

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

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

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

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

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

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

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

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

Hope some of that helps.


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

#364 Post by B.K. Johnson »

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

Excel under Wine

#365 Post by mikeslr »

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

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

As Mike Walsh said, FreeOffice is designed to be entirely compatible with microsoft's Excel. So, by the way is WPS Office.
Top
B.K. Johnson
Posts: 807
Joined: Mon 12 Oct 2009, 17:11

#366 Post by B.K. Johnson »

Macros and VBA makes the real deal.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine-4.9

#367 Post by version2013 »

My attempt at compiling wine-4.9

[wine-4.9 mirrors]

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

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

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

wine_DOC-4.9.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.9/
> _____wine-4.9_v1.1.pet

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

updated links at my homepage. see below.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine64-4.9

#368 Post by version2013 »

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

[wine-4.9 mirrors]

wine64-4.9_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.9.pet __________ tahrpup64 6.0.5
wine64_DOC-4.9.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.9_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
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#369 Post by bigpup »

version2013,

Thanks again for your work on Wine!!!
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-4.10

#370 Post by version2013 »

My attempt at compiling wine-4.10

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

[wine-4.10 mirrors]

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

wine_DOC-4.10.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.10/
> _____wine-4.10_v1.1.pet

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

updated links at my homepage. see below.
Last edited by version2013 on Mon 01 Jul 2019, 18:31, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine64-4.10

#371 Post by version2013 »

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

[wine-4.10 mirrors]

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

#372 Post by version2013 »

My attempt at compiling wine-4.11

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

[wine-4.11 mirrors]

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

wine_DOC-4.11.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.11/
> _____wine-4.11_v1.1.pet

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

updated links at my homepage. see below.
Last edited by version2013 on Thu 25 Jul 2019, 22:35, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine64-4.11

#373 Post by version2013 »

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

[wine-4.11 mirrors]

wine64-4.11_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.11.pet __________ tahrpup64 6.0.5
wine64_DOC-4.11.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.11_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
Lunos
Posts: 18
Joined: Fri 28 Jun 2019, 16:33

#374 Post by Lunos »

Hi! Quick question.
I downloaded and installed wine64-4.11_v4.1.pet, but when I try to run winecfg for example, I get a bunch of errors.
I'm using the latest version of XenialPup64.
https://pastebin.com/Ej3G8hkU

Help? :(
EDIT: Solved it. I just had to execute ldconfig again, like it was mentioned in this post.
Last edited by Lunos on Wed 03 Jul 2019, 15:21, edited 1 time in total.
Top
boof
Posts: 579
Joined: Wed 26 Sep 2012, 22:53

#375 Post by boof »

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

Wine-4.12.1

#376 Post by version2013 »

My attempt at compiling wine-4.12.1

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

[wine-4.12.1 mirrors]

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

wine_DOC-4.12.1.pet

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

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

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.12.1/
> _____wine-4.12.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

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

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 25 Jul 2019, 22:36, edited 1 time in total.
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine64-4.12.1

#377 Post by version2013 »

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

[wine-4.12.1 mirrors]

wine64-4.12.1_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.12.1.pet __________ tahrpup64 6.0.5
wine64_DOC-4.12.1.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.12.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
davids45
Posts: 1326
Joined: Sun 26 Nov 2006, 23:33
Location: Chatswood, NSW

64-bit Pups

#378 Post by davids45 »

G'day version2013,

Thanks for your continued work making Wine available in Puppy.
Working well in 32-bit Pups for many years and, with the right libraries, the 32-bit Wine runs in some 64-bit Pups.

But I think I need to I have a working Wine64 as this seems to be the eventual future - 64-bit OSs only.

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.

If you haven't seen it,
http://www.murga-linux.com/puppy/viewto ... 83#1030483
looks interesting as I too prefer to use an sfs over a pet so if I get a Wine64 pet to run, I'll turn it into an sfs for sharing to all my 64-bit Pups (as I do for the 32-bit Wine to my 32-bit Pups).

Thanks for any advice.

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

#379 Post by Mike Walsh »

@ David:-

I was having a read of something the other night which surprised me, in relation to WOW64, system32, etc. Were you aware that in a 64-bit Windows release, SysWOW64 apparently contains 32-bit executables/dlls, and the 64-bit ones are all found in system32?

No idea if that'll be of any use or not, but perhaps it may give you some clues.....check 'Properties' on some of these things, and see what ELF class you get showing in which directory. Sure sounds as confusing as hell..! :D

This article from MakeUseOf.com tells the tale...

https://www.makeuseof.com/tag/windows-system32/

".....<snip> On 64-bit versions of Windows, you’ll notice a few folder differences, like the separate Program Files (x86) directory. Something similar occurs with System32. In the C:\Windows folder on a 64-bit system, you’ll find a folder called SysWOW64 in addition to System32.

Take a look, and you’ll see that the two folders contain many files with identical names. Like Program Files (x86), Windows includes these two separate directories for compatibility with 32-bit programs. If a 32-bit program tried to load a 64-bit DLL, it would crash."


Now; naturally enough, you'd expect the system32 folder to contain the 32-bit stuff, and SysWOW64 to contain the 64-bit stuff, yes? Not so! Read on...


"But what’s strange is that on 64-bit systems, System32 has 64-bit files, while SysWOW64 contains 32-bit files. As it turns out, WoW64 stands for Windows 32-bit on Windows 64-bit. This is a service that allows the OS to properly run 32-bit programs, even on a 64-bit system.

Part of how it accomplishes this is by automatically redirecting 32-bit processes to use the proper folders. A 32-bit program, not even knowing that 64-bit software exists, will naturally try to access the System32 folder. But WoW redirects it to use the SysWOW64 instead. The same happens with Program Files.

Since many old 32-bit programs were hard-coded to access System32 and Program Files, this redirecting method allows 32-bit and 64-bit programs to both work on one system with ease. It’s a bit confusing, but now you know the reason for it.</snip>.......

Food for thought, perhaps?


Mike. :wink:
Top
version2013
Posts: 503
Joined: Mon 09 Sep 2013, 00:00
Location: Florida, USA
Contact:
Contact version2013

Wine-4.13

#380 Post by version2013 »

My attempt at compiling wine-4.13

[wine-4.13 mirrors]

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

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

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

wine_DOC-4.13.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.13/
> _____wine-4.13_v1.1.pet

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

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

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

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

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

Code: Select all

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

Code: Select all

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

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

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

updated links at my homepage. see below.
Top
Post Reply

Return to “Virtualization”