How to Install WINE on Slackware 12

ShellyCat · Post by **ShellyCat** » Thu Mar 13, 2008 7:19 am

Hello,

I read the README and the man pages and the User Guide.

They only say to run ./tools/wineinstall but it can't be found anywhere on my system!

I downloaded the package and used tar to extract it to my home directory (/root). I do not find "./tools" anywhere. Nothing in the documentation mentions the directory from which to install at all.

Plamen.Vassilev · Post by **Plamen.Vassilev** » Thu Mar 13, 2008 7:51 am

Do not run wine as root! Create regular user and then you can follow this
example:

o Optional: download compile and install latest fontforge from sourceforge.net
o Download wine sources from http://ibiblio.org/pub/linux/system/emu ... 57.tar.bz2 to some directory
o Extract wine sources with

Code: Select all

tar jxf wine-0.9.57.tar.bz2

o Enter the extracted sources directory:

Code: Select all

cd wine-0.9.57

o Execute

Code: Select all

./configure --with-x && make depend && make

o If everything went fine do a

Code: Select all

make install

as root, or run wine from the directory where you created it.
o Optional: run

Code: Select all

wineprefixcreate

Hope that helps.

Plamen

P.S. Did I mentioned NOT to run wine as root?

Bill Wells · Post by **Bill Wells** » Thu Mar 13, 2008 10:14 am

On Thursday 13 March 2008 05:51:23 Plamen.Vassilev wrote:

Do not run wine as root! Create regular user and then you can follow this
example:

o Optional: download compile and install latest fontforge from
sourceforge.net o Download wine sources from
http://ibiblio.org/pub/linux/system/emu ... 57.tar.bz2 to
some directory o Extract wine sources with
Code:
tar jxf wine-0.9.57.tar.bz2

o Enter the extracted sources directory:
Code:
cd wine-0.9.57

o Execute
Code:
./configure --with-x && make depend && make

o If everything went fine do a
Code:
make install

as root, or run wine from the directory where you created it.
o Optional: run
Code:
wineprefixcreate

Hope that helps.

Plamen

P.S. Did I mentioned NOT to run wine as root?

http://www.linuxpackages.net has a repository of programs that are
specifically tailored to be installed with Slackware's pkgtool program.

It usually takes a few days before one of the gurus that process the programs
accomplish their tasks and get the programs uploaded. My Wine is
perfectly "made" and pops up in KDE or the console.

and, never run wine as root.

Bill Wells

James McKenzie · Post by **James McKenzie** » Thu Mar 13, 2008 10:40 pm

ShellyCat wrote:

Hello,

I read the README and the man pages and the User Guide.

They only say to run ./tools/wineinstall but it can't be found anywhere on my system!

I downloaded the package and used tar to extract it to my home directory (/root). I do not find "./tools" anywhere. Nothing in the documentation mentions the directory from which to install at all.

Shelly:

You are going to read this again and again but here goes.

NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is
one reason to switch to Linux in the first place) and if something bad
were to happen, your entire system may be damaged...

James McKenzie

Dan Kegel · Post by **Dan Kegel** » Thu Mar 13, 2008 10:43 pm

<[email protected]> wrote:

You are going to read this again and again but here goes.

NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is
one reason to switch to Linux in the first place) and if something bad
were to happen, your entire system may be damaged...

We're saying this so many times a day ... time to automate the
warning. I'll send a patch.

James McKenzie · Post by **James McKenzie** » Fri Mar 14, 2008 9:38 pm

Dan Kegel wrote:

<[email protected]> wrote:

You are going to read this again and again but here goes.

NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is
one reason to switch to Linux in the first place) and if something bad
were to happen, your entire system may be damaged...

We're saying this so many times a day ... time to automate the
warning. I'll send a patch.

Clap...Clap...Clap. and a hearty thank you.

WINE and root should NEVER mix.

James

Plamen.Vassilev · Post by **Plamen.Vassilev** » Wed Mar 19, 2008 1:25 pm

Dan Kegel wrote:<[email protected]> wrote:
You are going to read this again and again but here goes.

NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is
one reason to switch to Linux in the first place) and if something bad
were to happen, your entire system may be damaged...
We're saying this so many times a day ... time to automate the
warning. I'll send a patch.

I am sorry to resurrect a dead thread, but just out of curiosity, Dan, what you think is the preferred behaviour when wine gets started by root? Should wine just print warning and then run, or probably it should die unless there is a special option on the command line like --yeah-I-know-I-am-root or --allow-root or something like that. Most users are running their applications via desktop/menu shortcuts so they won't see the warning (that's if they are running their graphic environment as root too). Maybe it should print a warning, then die. The warning should inform the user about the risks involved in running wine as root, and if they absolutely need to run wine as root then they should consult the documentation (where this option will be mentioned). If the warning itself contains option then it's almost guaranteed that the user will just set it and run wine again. On the other hand this is too restrictive... What do you think?

regards
Plamen

austin987 · Post by **austin987** » Wed Mar 19, 2008 1:29 pm

On Wed, Mar 19, 2008 at 1:25 PM, Plamen.Vassilev
<[email protected]> wrote:

Dan Kegel wrote:
<[email protected]> wrote:

You are going to read this again and again but here goes.

NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is
one reason to switch to Linux in the first place) and if something bad
were to happen, your entire system may be damaged...

We're saying this so many times a day ... time to automate the
warning. I'll send a patch.
I am sorry to resurrect a dead thread, but just out of curiosity, Dan, what you think is the preferred behaviour when wine gets started by root? Should wine just print warning and then run, or probably it should die unless there is a special option on the command line like --yeah-I-know-I-am-root or --allow-root or something like that. Most users are running their applications via desktop/menu shortcuts so they won't see the warning (that's if they are running their graphic environment as root too). Maybe it should print a warning, then die. The warning should inform the user about the risks involved in running wine as root, and if they absolutely need to run wine as root then they should consult the documentation (where this option will be mentioned). If the warning itself contains option then it's almost guaranteed that the user will just set it and run wine again. On the other hand this is too restrictive... What do you think?

regards
Plamen

See http://bugs.winehq.org/show_bug.cgi?id=10324

Plamen.Vassilev · Post by **Plamen.Vassilev** » Wed Mar 19, 2008 1:37 pm

Ah yes, I see that a discussion is already on. Thank you Austin

ShellyCat · Post by **ShellyCat** » Wed Mar 19, 2008 10:33 pm

Plamen.Vassilev wrote:Do not run wine as root!

Please let me clarify, because my question regarded installation...
...I am assuming I should compile and install as root, correct?

Thank you for the manual instructions...sometimes a compile/install is more dependable than packages.

(Sorry I took so long to check the post...I am in school and doing many tasks over vacation, so unfortunately I'm not as regular in checking forums as I used to be!)

Dan Kegel · Post by **Dan Kegel** » Wed Mar 19, 2008 10:53 pm

On Wed, Mar 19, 2008 at 8:33 PM, ShellyCat <[email protected]> wrote:

Please let me clarify, because my question regarded installation...
...I am assuming I should compile and install as root, correct?

No. Never compile as root. The only step to do as root is 'make install'.
- Dan

ShellyCat · Post by **ShellyCat** » Thu Mar 20, 2008 2:24 am

OK, I had an error message when I ran "wineprefixcreate" (as a regular user). I did a search and found only 1 post, and tried to do what it said: http://forum.winehq.org/viewtopic.php?t=242

Original post (I deleted from the other person's thread and moved here):

When I ran the "wineprefixcreate" (as a regular user) it got the "HTML rendering will be disabled" error.

Why does WINE care if Mozilla is installed? Will it refuse to render HTML pages, even via programs that can usually render HTML on their own, such as OpenOffice, Adobe Reader, etc???

Is there a fix?

The new problem is, when I tried to run "sh winetricks gecko" I got this error:

Code: Select all

Executing cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab
winetricks: line 234: cabextract: command not found
Note: command 'cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab' returned status 127.  Aborting.

So, I still wonder...will I not be able to view HTML in any applications I run in Wine? Why does it insist on Mozilla?

austin987 · Post by **austin987** » Thu Mar 20, 2008 2:38 am

On Thu, Mar 20, 2008 at 2:24 AM, ShellyCat <[email protected]> wrote:

OK, I had an error message when I ran "wineprefixcreate" (as a regular user). I did a search and found only 1 post, and tried to do what it said. I will cut there and paste here in just a sec.

Original post:

The new problem is, when I tried to run "sh winetricks gecko" I got this error:

Code:
Executing cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab
winetricks: line 234: cabextract: command not found
Note: command 'cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab' returned status 127. Aborting.

So, I still wonder...will I not be able to view HTML in any applications I run in Wine? Why does it insist on Mozilla?

Wine uses gecko to display html (in the same way windows uses IE). If
your application doesn't need it, you can safely ignore it. However,
if your app should be displaying HTML but doesn't, then install wine
gecko.

ShellyCat · Post by **ShellyCat** » Thu Mar 20, 2008 2:42 am

Plamen.Vassilev wrote: o Optional: download compile and install latest fontforge from sourceforge.net
o Download wine sources from http://ibiblio.org/pub/linux/system/emu ... 57.tar.bz2 to some directory
o Extract wine sources with...

I should not have been so impatient, and asked the purpose of fontforge...OK, its because Wine installs Windows fonts, and you need "fontforge" to do so, correct?

After starting "wine winefile" and seeing that the interface defaulted to some horrible fantasy-type text on me (though I could change the font used for file-browsing), I went back and installed fontforge. I verified the install by running "fontforge", which bought up the font-browsing GUI window.

Question: The fantasy font is still used in the "winefile" file browser...do I need to re-configure wine? Uninstall wine and compile and install all over again?

Lisa Denia · Post by **Lisa Denia** » Thu Mar 20, 2008 2:46 am

Hi,

Don't you wonder about this line?

winetricks: line 234: cabextract: command not found

Install the program cabextract, and it will work

. CAB is something
like an archiving format from Microsoft.

Have fun,
Lisa Denia

ShellyCat · Post by **ShellyCat** » Thu Mar 20, 2008 3:16 am

Lisa Denia wrote:Install the program cabextract

I'll get around to that...first, I'm wondering if I need to uninstall Wine, just re-configure, or what? (In order to fix the font problem)

Plamen.Vassilev · Post by **Plamen.Vassilev** » Thu Mar 20, 2008 3:32 am

ShellyCat wrote: I'll get around to that...first, I'm wondering if I need to uninstall Wine, just re-configure, or what? (In order to fix the font problem)

Yes, after installing fontforge, you can run ldconfig, and then reinstall wine.
Simplest way is to enter the sources directory and 'make clean'. Then repeat the installation steps (from ./configure...)

Hope that helps
Plamen

metalfanat · Post by **metalfanat** » Tue Oct 02, 2012 10:45 am

Hi. I want to put together a package for slackware 14. First. when done, the

sh wine.Slackbuild

compiler told me that we need a 32-bit version gcc. After install all the 32-bit version of the compiler, сonsole has the following message

Code: Select all

wine-1.5.14/tools/wrc/writeres.c
checking build system type... x86_64-slackware-linux-gnu
checking host system type... x86_64-slackware-linux-gnu
checking whether make sets $(MAKE)... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/SBo/wine-1.5.14':
configure: error: C compiler cannot create executables

List compiler installed

Code: Select all

gcc-4.7.1-i486-1             gcc-gfortran-4.7.1-x86_64-1  gcc-java-4.7.1-i486-1
gcc-4.7.1-x86_64-1           gcc-gnat-4.7.1-i486-1        gcc-java-4.7.1-x86_64-1
gcc-g++-4.7.1-i486-1         gcc-gnat-4.7.1-x86_64-1      gcc-objc-4.7.1-i486-1
gcc-g++-4.7.1-x86_64-1       gcc-go-4.7.1-i486-1          gcc-objc-4.7.1-x86_64-1
gcc-gfortran-4.7.1-i486-1    gcc-go-4.7.1-x86_64-1        gccmakedep-1.0.2-noarch-2

thanks.