SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to compile wine but I see an error message.
I tried first to change ARCH variable but didn't work. Any ideas?
checking build system type... x86_64-slackware-linux-gnu
checking host system type... x86_64-slackware-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for cpp... cpp
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
It looks like wine uses 32bit libs. Is there any way to workaround this?
As far as I know, WINE requires the 32 bit libraries. This has been discussed in several other threads. Slackware64-current is capable of using such 32 bit libraries, but currently it does not ship with them. Since Slackware64-current is still in development, that may or may not change. If not, the community will surely step up to provide an easy way to add them after the fact.
I had the same problem so I just used the package that I compiled on my Slackware 12.2 partition and installed it with the 32bit compatibility packages from slamd64 (aaa-elflibs, xlibs and gcc). It will work with just the first two but it is faster with the third.
I am going to try with BlueWhite64's packages tomorrow, though as BW64 uses a different directory structure I will have to do a bit of exploding, renaming and makepkg'ing.
The above test wasn't successful, but it could be something I did wrong.