Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 need to Switching gcc and g++ from i486-linux-gnu to i686-linux-gnu target
Why do you think that would help?
I'm sure you are ignoring a lot of differences between the situation that worked and the situation that failed. It is most likely one of the differences you are ignoring is responsible for the failure.
You haven't given enough information for us to make reasonable estimates of the correct diagnosis for your problem.
Recompiling gcc would be needed to make the change you think you need. You could download gcc source code and follow the included instructions and do that. But I suspect the process would be too difficult for you and more importantly wouldn't do you any good, because I'm pretty sure you are wrong about the gcc target even mattering.
There is also an option -march=i686 that can be used to make gcc produce roughly the same compiled code that it would have produced if gcc itself had been built for a target of i686. The makefile you are using for enigma probably would take such options via the CFLAGS environment variable, so you could compile enigma for i686 even using a gcc whose target is i486. That would be much easier than recompiling gcc itself. If you were correct (which I still really doubt) that the gcc target is a significant factor in your problem, the likely using -march=i686 would be as good as changing the gcc target.
Originally Posted by weibullguy
Are you sure the problem is the target and not the gcc version?
I would guess the problem is something else entirely, neither the target nor the gcc version. We don't know exactly what the OP tried on each machine, so it is reasonable to expect there are a wide variety of differences between the two situations.