Hello,

I am not a total Linux newbie, but this is my first foray into the mysterious world of compiling from source. Apparently there are no up-to-date binaries for Wine in Debian, so I can't just apt-get

I made a directory for the WINE source to extract to, but the graphical archiver would not recognize it, so I ended up extracting to the default /tmp.

Here is the output of the terminal so far:

c-24-18-244-87:/home/pad# mkdir .wine
c-24-18-244-87:/home/pad# cd tmp
bash: cd: tmp: No such file or directory
c-24-18-244-87:/home/pad# cd /tmp
c-24-18-244-87:/tmp# ls
gconfd-pad libgksu-yO0g8K orbit-root wine-0.9.25
gconfd-root mapping-pad ssh-paNdPi5054 wine-0.9.25.tar.bz2
keyring-jSJuA1 orbit-pad virtual-pad.SIpZmW
c-24-18-244-87:/tmp# cd wine-0.9.25
c-24-18-244-87:/tmp/wine-0.9.25# ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc -m32
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
c-24-18-244-87:/tmp/wine-0.9.25# config.log
bash: config.log: command not found
c-24-18-244-87:/tmp/wine-0.9.25#


How do I look at 'config.log'? Are there build dependencies? The WINE HQ instructions say to look for them in the output of configure, but I don't know how to interpret what I'm looking at.

System:
AMD 64 3800+, 1GB RAM, 64 Studio distro (a media authoring optimization of Debian)

FWIW, here are links to some software I want to run in WINE. If you're musically inclined, they might be of interest:

http://www.giamusic.com/scstore/P-au...assistant.html
http://www.tune-assistant.com/

Thanks,

Paul in Seattle

Open a console (that icon in the tray that looks lide a monitor, probably with a scallp shell superimposed: in you don't already know it, that's the command-line interface, or whatever you want to call it).

enter the command: su. you will be prompted for a password. enter the root users password.

run the command: updatedb. depending on system speed and number of files on the system, it could take a minute or two to run to completion.

when it's done, run the command: locate config.log. Other apps may have generated a log with the same name. so, look for the one with a date and time stamp for the time you compile wine.

In bash, you need to cd to the folder that contains the file, then run the command: cat config.log, or, from anywhere in the system, give the full path to config.log. as in, cat /tmp/wine-0.9.25/config.log (or whereever it is).

if the file is more that one screen long, you can make it pause at one screenfull by piping the command through less: cat config.log | less. Press the space bar to see the next page (or use pageup, pagedown, up or down arrow keys) to scroll forward or backward.

You need the binutils package installed and for that matter make sure you have build-essential as well.

Hello, Bridgedriver and Stphen Cormier, and thanks for replying.

The only log that showed up was /var/log/fontconfig.log . Can this be relevent? I am doubtful. I will post it if you think it will help.

binutils and buld-essential are both installed by default.

-PD

The log you would be looking for should be in the directory you compile/configure in, for the cannot create executables error that is usually the missing binutils package so I really have no idea what is going on here now. Ok just took a look at the output again this is a 64bit install your trying to compile on right? If so I do not believe that wine works on 64bit you would need to do what is called a chroot 32bit install then install the wine in it.

Aha, the Curse of 64 Bits strikes again! I should have suspected. I've encountered it before, with Flash 9 and Opera. That's why I have the 32 bit Ubuntu install on another partition.

After Googling "chroot 32bit", I'm pretty overwhelmed. Can you point me to the least horrendous install?

It may be easier to install in my 32-bit Ubuntu system on the same computer. WINE works on it, though there's no sound. Everybody seems to have the same problem on Ubuntu, so maybe I could uninstall the binaries, and compile WINE from source there.

Have you installed a chroot 32bit? How involved is it?

--Paul