Puppy Linux Discussion Forum

version2013 · Joined: 08 Sep 2013 Posts: 382 Location: Florida, USA

My attempt at compiling wine-2.0.4

[wine-2.0.4 mirrors]

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

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

wine_DOC-2.0.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 denotes a link to a mirror for either a directory or file.
ie. Look for the ">" adjacent to a
> directory/
> file

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

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

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

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

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

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

version2013 · Joined: 08 Sep 2013 Posts: 382 Location: Florida, USA

My attempt at compiling wine-3.0-rc5

[wine-3.0-rc5 mirrors]

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

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

wine_DOC-3.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 denotes a link to a mirror for either a directory or file.
ie. Look for the ">" adjacent to a
> directory/
> file

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

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

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

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

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

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

Lassar · Joined: 08 Jul 2014 Posts: 221

Is there any 32 bit wine compiled for Xenialpup64?

I have tried using the Lubuntu way to make a wine sfs
with all the dependices, but that results in a sfs about
190 mb in size.

Way too big.

mikeslr · Posted: Thu 11 Jan 2018, 16:15 Post subject: Wine SFS -- easy to make your own

Hi Lassar,

You don't need an SFS specifically made for Xenialpup64. Wine will run under any Puppy. But you must install the 32-bit compatibility application created for you version. As I always run Wine --I have one xp program I consider essential-- I converted the 32-bit compatibility SFS into a pet. You obtain the 32-bit compatibility libs for and in Xenialpup64 by opening a terminal and typing "sfsget"-- without the quotes. A window will open, and downloading the 32-bit compatibility SFS is one of your choice.

Having downloaded it, I created a folder --right-click empty space, select New>Directory-- which I named 32bit_xen64_libs, and opened it. I then Right-Clicked the 32-bit compatibility SFS, Selected "View" (which mounts it), dragged its contents into the 32bit_Xen64_libs folder and selected Copy. Once it was copied, I right-clicked the 32-bit compatibility SFS to unmount it.

Browsing up to the parent folder of 32bit_xen64_libs, so that I could see it as a folder, I right-clicked an empty space and selected Window>terminal here. Then I typed, Code --without the quotes: "dir2pet 32bit_xen64_libs".

Whether you create a pet or just load the 32bit compatibility SFS, you must configure your system to use it. To do that, open a terminal and type, without the quotes, Code: 'ldconfig'. The first character is a small "El". It should take some time before the terminal prompt appears again. If it appears immediately, enter the terminal command again. And I recommend, before trying to get Wine working that you try some simple 32-bit application that you know works.

Creating a wine sfs is pretty much the reverse of the above. Download one of Version2013's pets. As Wine 3 is still in development, I'd suggest, for now, using the last of the "2" series. The "2" series has 64-bit application support, and those toward the end of this thread are the latest. After you download it, Right-Click the pet and from the popup menu select UExtract. An Extracted folder will be created and within it will be another just named Wine with its version number, Right-click an empty space next to that folder, Select Window>terminal here and type "dir2sfs EXACT_NAME_OF_FOLDER" -- without the quotes.

Unless you're using Wine-portable, see here, http://murga-linux.com/puppy/viewtopic.php?p=971452#971452, the FIRST thing you'll have to do after installing a Wine pet or loading a Wine SFS is open a terminal and type "wine winecfg" to create and configure the Wine environment.

Note, however, that since Wine 1.5.1.8 version2013 has not included Menus in his builds. If you can't live without Menus --or chose not to build your own, see here, http://www.murga-linux.com/puppy/viewtopic.php?p=882255#882255-- there's a better way to create a Wine SFS. With the instructions given above you would have to either install a menu pet or deconstruct it and move its contents into the proper places in the Wine folder before running dir2sfs.

Install, PaDS from here, http://murga-linux.com/puppy/viewtopic.php?t=81511 and unrpm-all.pet from here: http://www.murga-linux.com/puppy/viewtopic.php?p=940751#940751. Place both the wine pet and the wine-menu pet in an EMPTY folder, NOT IN /root, and give that folder a meaningful name, such as wine2. Right-Click the folder --you have to see it as a folder-- and select Combine to SFS. In due course, an SFS with the name of your folder will be created in /root. It will contain the files from all the pets you had in that folder.

mikesLr

version2013 · Joined: 08 Sep 2013 Posts: 382 Location: Florida, USA

My attempt at compiling wine-3.0-rc6

[wine-3.0-rc6 mirrors]

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

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

wine_DOC-3.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 denotes a link to a mirror for either a directory or file.
ie. Look for the ">" adjacent to a
> directory/
> file

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

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

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

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

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

I compiled using racy 5.5

mirrors | /distro/racy5.5/racy-5.5.iso
mirrors | /distro/racy5.5/devx_racy_5.5.sfs

This puppy distro uses glibc 2.10.1
The Wine files listing 'racy 5.5' will possibly:
- fail with a glibc before 2.10.1
- succeed with a glibc of 2.10.1 and above

To see what glibc your puppy has.

bigpup · Posted: Sat 20 Jan 2018, 03:05 Post subject:

Thanks again for your support of Wine for Puppy!!!

musher0 · Posted: Sat 20 Jan 2018, 05:07 Post subject:

Hi version 2013.

Along with ally, our archivist, you're one of Puppy's unsung heroes!!!

Speaking of which... are there any song-writers around here? Wink

BFN.

p310don · Posted: Sat 20 Jan 2018, 10:16 Post subject:

version2013 · Joined: 08 Sep 2013 Posts: 382 Location: Florida, USA

My attempt at compiling wine-3.0

[wine-3.0 mirrors]

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

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

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

wine_DOC-3.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/3.0/
> _____wine-3.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 | page]

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

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

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

I compiled using puplet: Puppies 4.31.1 by forum member 'ttuuxxx'

mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso
mirrors | /distro/4.3__1/devx_430.sfs

This puplet uses glibc 2.6.1
The Wine files listing 'puppy 431' will possibly:
- fail with a glibc before 2.6.1
- succeed with a glibc of 2.6.1 and above

To see what glibc your puppy has.

version2013 · Joined: 08 Sep 2013 Posts: 382 Location: Florida, USA

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

[wine-3.0 mirrors]

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

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

I compiled using tahrpup64 6.0.5

This puppy distro uses glibc 2.19
The Wine files listing 'tahrpup64 6.0.5' will possibly:
- fail with a glibc before 2.19
- succeed with a glibc of 2.19 and above

To see what glibc your puppy has.

musher0 · Posted: Thu 25 Jan 2018, 18:33 Post subject:

Hello, version 2013.

The download link does not work.It keeps recycling to the wait protocol.
(old opera 12.16) TIA for a solution.

Edit: Ok got it through PaleMoon but I had to deactivate uBlock Origin.
Downloading now.

Thanks.

fabrice_035 · Joined: 28 Apr 2014 Posts: 505 Location: Bretagne / France

Thanks for .pet, i tried wine-3.0_v3.2.pet for puppy tahrpup 6.0.6 32bits.

Have you an idea to resolv that (strange font)

(see attachment)

Regard

fabrice_035 · Joined: 28 Apr 2014 Posts: 505 Location: Bretagne / France

Hi,

Reply himself, found solution: rename /usr/share/font as /usr/share/_font and link /usr/share/wine/font --> /usr/share/font
Now is good for wine but bad for linux program such as Firefox run with horrible font.
Rolling Eyes

musher0 · Posted: Mon 29 Jan 2018, 20:00 Post subject:

HI fabrice_035.

Probably not the best solution. You can download wine-specific fonts with a wine
companion utility called "Winetricks". Please see here.

IHTH.

fabrice_035 · Joined: 28 Apr 2014 Posts: 505 Location: Bretagne / France

Hi musher0,

Good, winetrick make wine finaly work fine. Just before need install cabextract from PPM

Regard