[SOLVED] Wine Install fails at line 291

Tim Johnson · 01-30-2010, 06:49 PM

Using slack 13.0 32-bit.
I'm using http://connie.slackware.com/~alien/s...ine.SlackBuild
with one modification only: The version number at $SRCVER was changed to 1.1.37

The script has failed with the following error message:

Code:

wine.SlackBuild FAILED on line 291!

The code at that line is

Code:

cat $PKG/install/slack-desc | grep "^${PRGNAM}" > $OUTPUT/${PRGNAM}-${VERSION}-${ARCH}-${BUILD}${TAG}.txt

I also have noted the following (in part) outputs previous to the error

Code:

usr/lib/wine/mstask.dll.so
usr/lib/wine/wineaudioio.drv.so
usr/lib/wine/ddraw.dll.so
usr/lib/wine/libsensapi.def
usr/lib/wine/liboleacc.def
usr/lib/wine/urlmon.dll.so
usr/lib/wine/winnls32.dll.so
......
usr/share/wine/fonts/tahomabd.ttf
usr/share/wine/fonts/ssee874.fon
usr/share/wine/fonts/sserifer.fon
usr/share/wine/fonts/symbol.ttf
usr/share/wine/fonts/vgasys.fon
usr/share/wine/fonts/smallee.fon
usr/share/wine/fonts/vgasysg.fon

It appears to me that a successful build may have been made at
/tmp/build/package-wine/usr
But the install has failed.
Please advise how to procede from here.
thanks

Alien Bob · 01-30-2010, 07:16 PM

If it failed on that line (for unknown reasons) then at least the package has been created. Look in /tmp for wine-1.1.37-i486-1alien.tgz (assuming you left the 'alien' tag in).

Eric

Tim Johnson · 01-30-2010, 07:48 PM

Quote:

Originally Posted by Alien Bob

If it failed on that line (for unknown reasons) then at least the package has been created. Look in /tmp for wine-1.1.37-i486-1alien.tgz (assuming you left the 'alien' tag in).

Eric

It is there - at the top of /tmp. Along with logs. Let me know how to
procede and whether you may want to look at logs. Also, it is late here
in Alaska and I may not be able to answer until later.

thanks Eric
tim

zakonnik · 01-30-2010, 08:50 PM

http://scxd.info/pub/packages/xap/wi...36-i686-1X.txz

XGizzmo · 01-31-2010, 05:28 AM

Sounds like maybe you did not copy the slack-desc file along with the SlackBuild. When dealing with SlackBuilds you need more or less all the files in the directory containing the SlackBuild.

vdemuth · 01-31-2010, 06:44 AM

Talking of Alien Bob's wine. He has also provided a slack64 version. Having installed it though, it errors out when attempting to run it. Does it require the multilib packages to be installed?

Alien Bob · 01-31-2010, 06:47 AM

Quote:

Originally Posted by vdemuth

Talking of Alien Bob's wine. He has also provided a slack64 version. Having installed it though, it errors out when attempting to run it. Does it require the multilib packages to be installed?

Yes it does.

Eric

vdemuth · 01-31-2010, 06:52 AM

Thought so. Thanks for the prompt reply. Time to bite the bullet then and go multilib.

samac · 01-31-2010, 08:44 AM

Quote:

Thought so. Thanks for the prompt reply. Time to bite the bullet then and go multilib.

Don't worry it is painless and works perfectly. Remember to modify your slackpkg blacklist, if you upgrade that way, it will save you grief. Also re-install your nvidia driver with 32-bit extensions if you use nvidia cards.

samac

Tim Johnson · 01-31-2010, 10:49 AM

Quote:

Originally Posted by XGizzmo

Sounds like maybe you did not copy the slack-desc file along with the SlackBuild. When dealing with SlackBuilds you need more or less all the files in the directory containing the SlackBuild.

I did get an error originally when I did not have the slack-desc file in
the same directory as the SlackBuild file. Then I just copied the slack-desc template to slack-desc.

Tim Johnson · 01-31-2010, 10:54 AM

Quote:

Originally Posted by Alien Bob

If it failed on that line (for unknown reasons) then at least the package has been created. Look in /tmp for wine-1.1.37-i486-1alien.tgz (assuming you left the 'alien' tag in).

Eric

Eric, is not wine-1.1.37-i486-1alien.tgz the package? And if so,
should I not be able to runinstallpkg against it?

But, also, if you would like me to do any further trouble-shooting,
I would be happy to do so. I am a programmer also, not so much with
shell script tho'.

tim

Alien Bob · 01-31-2010, 10:58 AM

Quote:

Originally Posted by Tim Johnson

Eric, is not wine-1.1.37-i486-1alien.tgz the package? And if so,
should I not be able to runinstallpkg against it?

Yes that is the package, and you could install it. However, as was explained in another post, you're probably missing the slack-desc file which makes it an incomplete package (it will have no description when you install it, nor will it have a description in /var/log/packages).

Quote:

But, also, if you would like me to do any further trouble-shooting,
I would be happy to do so. I am a programmer also, not so much with
shell script tho'.

If indeed the slack-desc file is missing, all you need to do is download that to the directory of the wine.SlackBuild and then rebuild the package.

Eric

tim[/QUOTE]

Tim Johnson · 01-31-2010, 01:49 PM

Quote:

Originally Posted by Alien Bob

If indeed the slack-desc file is missing, all you need to do is download that to the directory of the wine.SlackBuild and then rebuild the package.

Eric

Well, I did have the slack-desc template in that directory,
but obviously - your system was looking for your own slack-desc. Once
I installed that, the build was successful.
Again, I'm running out of time here. Weekends just get in the way of
computing

.
Another question:
When I go to run installpkg, must it be run from /tmp or can it be run
from a directory of my choice?

Tim Johnson · 02-01-2010, 07:04 PM

OK. Installation without a problem! I copied the tarfile from
/tmp then:

Code:

installpkg --warn wine-1.1.37-i486-1alien.tgz > preview.txt

Reviewed the output file and found no obvious problem
and then ran

Code:

installpkg wine-1.1.37-i486-1alien.tgz

I have one remaining question:
Try as I have, I can't find how to mark this thread as solved.
Let me know and I will mark it as such.
thanks to all.
tim

Hangaber · 02-01-2010, 11:52 PM

Quote:

Originally Posted by Tim Johnson

I have one remaining question:
Try as I have, I can't find how to mark this thread as solved.
Let me know and I will mark it as such.
thanks to all.

Top of the screen (above the first "visible" post if you scroll up)... Thread Tools -> Mark thread as solved.