Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
configure: creating cache config.cache
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.
Configure failed, aborting install.
i now installed gcc 4.3.0 whit g++ completely and still got this same message.
ahh now my link did not have a slackware package but I thought you might see that with the other distros you need to d/l a number of 32 bit packages so the compile will work....and you probably need the source not the slackware tgz.
To repeat build a 32 bit app on 64 bit system requires all dependencies to be met.
pls look at what the other distros require....but when you use source to do the configure.....configure will complain its missing package x then package y so you will find out how to do it.
2) I am not suggesting you d/l slack as 32 bit....but IMHO this is still the weakness of 64 bit...that it can be a struggle to build packages only coming as 32. I have a amd 64 bit cpu but still run 32 bit.
There are other threads on the alleged difference between 32 & 64 so make up your own mind.
but if (1) gets too hard for you....post back but not here....you are better off posting in slackware forum.....and choose a title like
error (whatever) building wine on 64 bit system