LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   wine and slackware (http://www.linuxquestions.org/questions/linux-software-2/wine-and-slackware-210275/)

paul62 07-27-2004 02:28 PM

wine and slackware
 
I have wine build 20040716 installed in slackware 9.1. I successfully unpacked the tarball, if I want to run notepad what would the command be to run notepad? I have windows 98 installed on another partition on the same hard drive, what windows programs can be ported to wine I would really appreciate a general idea of how to get started.

Komakino 07-27-2004 02:37 PM

Well that depends on where notepad is installed. There is a version of notepad included anyway which can be run by:
wine notepad
but why anyone would want to run notepad on Wine I have no idea.
If your windows partition is /dev/hda1 and you mount it to /mnt/hda then I imagine notepad would be at:
/mnt/hda/Windows/notepad.exe and so can be run with:
Code:

wine /mnt/hda/Windows/notepad.exe
but obviously that needs altering to suit your path and environment.

You also need to work on your punctuation; that last sentence is horrible.

paul62 07-27-2004 02:53 PM

I tried the command wine notepad.exe when I am logged in as root and I get the message "command not found" what might I be doing wrong?

Komakino 07-27-2004 03:07 PM

Looks like you don't have wine installed. Or it could just be that it's not in root's path. Try it as a normal user and if you still get nothing then post the output of:
Code:

find /usr -iname "wine"
here.

paul62 07-27-2004 03:27 PM

The result of this last command was nothing , I tried not logging in as root running th ecommand and it just went to bash.

Komakino 07-27-2004 03:48 PM

Then you don't have wine installed.

Hang on...you say you "Successfully unpacked the tarball"...have you actually compiled it though?!

(i.e. have you run tools/wineinstall ?)

paul62 07-28-2004 12:32 PM

I got the tarball unpacked through using the exdtract command in midnight commander, and assumed that would be compiling it, what is the command for compiling it? I woould reallly appreciate the help.

EArthquake 07-28-2004 02:20 PM

u have a step by step explained in readme or install file of unpacked tarball

Komakino 07-28-2004 04:03 PM

Yep, read the README or INSTALL files (I'm not capitalising to be rude, they usually are all in caps!)

Unpacking is just like extracting a zip file - it doesn't compile the program.

Now you'd better hope you installed those devel packages....

Bebo 07-28-2004 05:11 PM

Perhaps this is not true in the case of Wine, but the usual way to compile a program from source are these steps:
Code:

./configure
make
<su to root>
make install

However, doing it this way might make it difficult to remove the program later, since the files are spread out on your file system. Some Makefiles will provide an uninstall target, so that one can use make uninstall to remove the files. Now, this would of course require you to keep the source which one might not always want to do. So, the alternative way is to use the very nice program checkinstall instead of the make install:
Code:

./configure
make
<su to root>
checkinstall

checkinstall can make rpm, deb, and tgz packages. Works like a charm :)

Cheers

Komakino 07-28-2004 05:32 PM

Quote:

Originally posted by Bebo
Perhaps this is not true in the case of Wine, but the usual way to compile a program from source are these steps:
Code:

./configure
make
<su to root>
make install

However, doing it this way might make it difficult to remove the program later, since the files are spread out on your file system. Some Makefiles will provide an uninstall target, so that one can use make uninstall to remove the files.
Cheers

No, it's not how Wine does it. Wine uses a script called wineinstall in the tools subdirectory. And compiling software generally doesn't make it hard to remove if you know what you're doing. Whilst a few more complicated programs spread themselves out, most go no further than putting a folder in the /usr/shared directory and a binary in /usr/bin. Occasionally you get a library in /usr/lib but even so, to remove the whole thing is a case of:
Code:

rm -rf `whereis wine`

I also want to add (and I mean no disrespect) that I think you [Paul62] have chosen the wrong distribution for a beginner. Whilst I believe Slackware to be the best distro, and it's the only one I've ever been truly happy with, I think you'll find something more geared towards the novice user to be much better to find your feet with linux. Slackware requires mainly manual configuration, whereas something like Mandrake or Fedora will have a lot of tools to do the job for you.

That's my 2 pence anyway.

Bebo 07-28-2004 05:57 PM

"If you know what you're doing" - or if you want to make life a bit simpler and don't want to chase files all over the place.

Cheers

Komakino 07-28-2004 06:02 PM

Quote:

Originally posted by Bebo
"If you know what you're doing" - or if you want to make life a bit simpler and don't want to chase files all over the place.

Cheers

Well if settling dependencies and having to wait for new packages to be available is your thing...

Bebo 07-28-2004 06:30 PM

What does that have to do with whether you do an ordinary make install or a checkinstall?

Komakino 07-28-2004 07:58 PM

Quote:

Originally posted by Bebo
What does that have to do with whether you do an ordinary make install or a checkinstall?
I apologise, I missed that bit of your post. Actually, this wasn't supposed to end up as an argument about install methods, I was initially just trying to demonstrate that it isn't hard to remove a normally installed program if you know how to make use of "output as input" (which is a phrase I've just coined...what's it really called?!)


All times are GMT -5. The time now is 02:38 PM.