Problem installing from source, 1.3.2 "..prelink not f

[RaistlinM531]

Hi all!

Trying to get magic workstation (www.magicworkstation.com) to run correctly. My distro (BT4R1) comes with an older version of wine, so I uninstalled it then installed Wine Stable 1.2. Compiled it manually, got it everything it needed save one thing from the ./configure and it seemed to install fine, but it did not fix my problem. There are still some game breaking graphical isssues with it. Ok, so I decided I would try the latest version, since the latest stable didn't work. Uninstalled previous version. Downloaded 1.3.2. When I run 'make ./configure' I get two errors at the end:

configure: libmpg123 development files not found (or too old), mp3 codec won't be supported.

configure: WARNING: prelink not found, base address of core dlls won't be set correctly.

I am worried about the second one, obviously. The first one was the one thing with the 1.2 install I could never get to work, but it installed fine w/o it. This second one seems to be a bigger deal. I went ahead and ran 'make depend.' Seemed to work, but when I run just 'make' this is what it gives me:

root@bt:/bin/wine-1.3.2# make
make[1]: Entering directory `/bin/wine-1.3.2/tools'
make[1]: `makedep' is up to date.
make[1]: Leaving directory `/bin/wine-1.3.2/tools'
make[1]: Entering directory `/bin/wine-1.3.2/libs/port'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/bin/wine-1.3.2/libs/port'
make[1]: Entering directory `/bin/wine-1.3.2/libs/wine'
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DWINE_UNICODE_API="" -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wno-unused-result -g -O2 -o debug.o debug.c
debug.c: In function 'debug_usage':
debug.c:180: warning: ignoring return value of 'write', declared with attribute warn_unused_result
At top level:
cc1: error: unrecognized command line option "-Wno-unused-result"
make[1]: *** [debug.o] Error 1
make[1]: Leaving directory `/bin/wine-1.3.2/libs/wine'
make: *** [libs/wine] Error 2

Not sure if 'this' problem is related to the problem I saw in ./configure, but I wouldn't bet against it, especially since a previous version seemed to install fine.
Any help would be appreciated, thanks!

[James McKenzie]

On 9/12/10 10:28 AM, RaistlinM531 wrote:

Hi all!

Trying to get magic workstation (www.magicworkstation.com) to run correctly. My distro (BT4R1) comes with an older version of wine, so I uninstalled it then installed Wine Stable 1.2. Compiled it manually, got it everything it needed save one thing from the ./configure and it seemed to install fine, but it did not fix my problem. There are still some game breaking graphical isssues with it. Ok, so I decided I would try the latest version, since the latest stable didn't work. Uninstalled previous version. Downloaded 1.3.2. When I run 'make ./configure' I get two errors at the end:

configure: libmpg123 development files not found (or too old), mp3 codec won't be supported.

You will have to find mpg123 development files for your distribution.
They cannot be included with Wine due to legal issues.

configure: WARNING: prelink not found, base address of core dlls won't be set correctly.

Cannot help you with this one.

James McKenzie

[DanKegel]

On Ubuntu, one could just do
sudo apt-get install prelink

but I don't think it's urgent you have prelink installed, unless
you plan to run apps that mess with other apps by injecting things
into their memory space.

I think you're getting ahead of yourself. Have you checked the appdb
page for that app,
http://appdb.winehq.org/objectManager.p ... n&iId=5661
? It has a couple hints that might help.

[RaistlinM531]

Hi all, thanks for the help thus far.

So I installed prelink which does take care of the ./configure error. I only have the one other error in the config now, which I am fairly sure is not a part of the 'make' problem since I was able to compile 1.2 with the same error. After fixing the prelink, i run make depend again and again make, and come back with the same error:

/bin/wine-1.3.2# make
make[1]: Entering directory `/bin/wine-1.3.2/tools'
make[1]: `makedep' is up to date.
make[1]: Leaving directory `/bin/wine-1.3.2/tools'
make[1]: Entering directory `/bin/wine-1.3.2/libs/port'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/bin/wine-1.3.2/libs/port'
make[1]: Entering directory `/bin/wine-1.3.2/libs/wine'
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DWINE_UNICODE_API="" -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wno-unused-result -g -O2 -o debug.o debug.c
debug.c: In function 'debug_usage':
debug.c:180: warning: ignoring return value of 'write', declared with attribute warn_unused_result
At top level:
cc1: error: unrecognized command line option "-Wno-unused-result"
make[1]: *** [debug.o] Error 1
make[1]: Leaving directory `/bin/wine-1.3.2/libs/wine'
make: *** [libs/wine] Error 2



I did check the app database and did see that it is apparently working better with version 1.1.42. I did know there was a previous version that it did work with (via a mws forum) but didn't know the version number. I just kinda figured the latest stable one would do the trick. I might be interested in running other things in WINE besides this in the long term, (world of warcraft if it is possible) so I would like the most up to date version that runs this thing, but obviously the next thing I will try is this previous version. While I do that today, if anyone has any idea about the error above, I'd love to hear it! Thanks!

[Frédéric Delanoy]

On Mon, Sep 13, 2010 at 14:07, RaistlinM531 <[email protected]> wrote:

Hi all, thanks for the help thus far.

So I installed prelink which does take care of the ./configure error. I only have the one other error in the config now, which I am fairly sure is not a part of the 'make' problem since I was able to compile 1.2 with the same error. After fixing the prelink, i run make depend again and again make, and come back with the same error:

/bin/wine-1.3.2# make
make[1]: Entering directory `/bin/wine-1.3.2/libs/wine'
gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -DWINE_UNICODE_API="" -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wno-unused-result  -g -O2  -o debug.o debug.c
debug.c: In function 'debug_usage':
debug.c:180: warning: ignoring return value of 'write', declared with attribute warn_unused_result
At top level:
cc1: error: unrecognized command line option "-Wno-unused-result"
make[1]: *** [debug.o] Error 1
make[1]: Leaving directory `/bin/wine-1.3.2/libs/wine'
make: *** [libs/wine] Error 2

I did check the app database and did see that it is apparently working better with version 1.1.42. I did know there was a previous version that it did work with (via a mws forum) but didn't know the version number. I just kinda figured the latest stable one would do the trick. I might be interested in running other things in WINE besides this in the long term, (world of warcraft if it is possible) so I would like the most up to date version that runs this thing, but obviously the next thing I will try is this previous version. While I do that today, if anyone has any idea about the error above, I'd love to hear it! Thanks!

The gcc you're using errs about the "-Wno-unused-result".
Either use another gcc or (probably easier), remove the
"-Wno-unused-result" parts from configure and configure.ac file then
run configure and make (I'm not too familiar with autoconf, so it
might not be sufficient, but you could give it a try).

Hope this helps,

Frédéric

[RaistlinM531]

Ok, thats something to try. I've now tried all of the 1.3.x variations, and they all stall out on me at some point during 'make', although, interestingly enough, not at the same spot. Anyways, I reinstalled 1.2 just to make sure I 'could' and that it wasn't some weird uninstall issue. 1.2 installed fine again, but it takes this system two hours to compile this thing.

That being said, here's a more newb question I bet someone reading this can answer -

Atm I do have a working 1.2 install. Can I do what the above poster said to a 1.3.x release and 'make' it without f'ing up my current install? I would imagine having two Wine's installed side by side is a recipe for disaster. Thanks!

[dimesio]

Atm I do have a working 1.2 install. Can I do what the above poster said to a 1.3.x release and 'make' it without f'ing up my current install? I would imagine having two Wine's installed side by side is a recipe for disaster. Thanks!

So don't install it. Wine can be run from the build directory. If you really want to install multiple versions, search the forum; this question has come up before.

[Frédéric Delanoy]

On Mon, Sep 13, 2010 at 19:04, RaistlinM531 <[email protected]> wrote:

Ok, thats something to try. I've now tried all of the 1.3.x variations, and they all stall out on me at some point during 'make', although, interestingly enough, not at the same spot. Anyways, I reinstalled 1.2 just to make sure I 'could' and that it wasn't some weird uninstall issue. 1.2 installed fine again, but it takes this system two hours to compile this thing.

BTW, if you want to speed up compilation, you can use ccache.
E.g. CC="ccache gcc" ./configure

[RaistlinM531]

So how do I run it from the build directory then? And I certainly 'don't' want to run multiple copies of WINE on my rig. I would just like to know how far in the build process I can go before my currently stable version goes to toast.

And to be above poster, thanks for the info about ccache. That will hopefully save me a bundle of time in the future. Thus far I've blown four hours on two installs of 1.2.

Thanks to all!

raist

[dimesio]

So how do I run it from the build directory then?

To run an app using an uninstalled version of Wine either cd to the build directory and use the command ./wine, or use the full path to the Wine you want to use in the command line. You'll have to do the latter if the app you want to run is fussy about where it's started from.

I would just like to know how far in the build process I can go before my currently stable version goes to toast.

"Make" alone won't do anything to your installed version; it's "make install" that would overwrite it.

[RaistlinM531]

Awsome, thats exactly what I needed to know. I don't have time to work on it today, but I'll post again once I've tried to get another install going. But after all the time this has taken I feel loads better knowing I can just keep trying 'make' w/o having to worry about messing up what is currently running fine. Ty so much!