Ok reading over all this it really appears that this
learning experience isn't going too well
So.. here's what I think:
You are pretty much not really understanding what each command you are executing, this could be a very big reason for not getting very far. It's important you understand
what we are having you do so:
1. You can execute them correctly, and:
2. You can apply them to other problems you encounter.
So I will try to explain things as I go, please pay attention to what you are doing, and if you have questions about
any part of it, please ask. This does mean though that you should also do your best to provide full and complete error messages to us. To do that you'll need to either have a working floppy drive that you can easily copy files to from linux (simple text files), a CD Burner that is working in linux and that you can easily use (aware of how to burn CD's), OR a fat32 partition so you can copy your files from linux to windows so you can post up the exact error messages for us. Just let us know if you have any of these available.
Ok, so it looks like we are trying to get your current gcc off there (gcc 3.x) and put an older version on (gcc 2.x). I don't think this is necessary, instead, since most of your apps (including your current kernel) are most likely going to be compiled with gcc 3.x and that's what you've got on your system. If I'm wrong, please, let me know. To find out, open up a terminal and as root type:
rpm -qa | grep gcc
And post up what you get returned. To get to root inside a terminal (assuming you are logged in as a user like you should be), type this:
su -
Which will switch from the current user to root. It will then prompt you for the root password, enter it and you'll automatically be in root's home directory (/root on most systems) which means you'll then need to cd (change directories) to the directory you were working in. To stop from having to cd everytime you switch to root from your working directory (a working directory means the directory you are performing functions in, and you briefly need root priviledges) you add the -m to su, so this command will keep you in your current directory:
su -m
Ok, so now it looks like you also need to show us whether or not you've got your current kernel sources/headers installed, so, again as root inside this terminal type:
rpm -qa | grep kernel
And also post the results of listing the contents of /usr/src Do this by typing:
ls -la /usr/src
What these commands do:
ls = List files
-a = list all files including hidden
-l = Show all the information about these files
/usr/src = the location that your kernel source is expected to be located
Also, a few things about forums:
1. When you post a question you usually shouldn't expect people to immediately reply; if they do, cool, if not, well that's normal.
2. Don't ask them to "hurry and reply" because regardless of what you mean by that, it appears that you are trying to rush them when helping you.
3. Post up full error messages, "Returned something about kernel something" is really not helpful at all. However "I executed:
./configure --enable-mysql
And it returned:
mysql does not exist" is a little better, a full error like:
Code:
bash-2.05a$ make
make: *** No targets specified and no makefile found. Stop.
Is much better and is ideal to help us see what's actually going on and what has actually been executed.
Now a few things on getting error messages:
You can send output to an actual text file so it makes it easier to carry over to your other OS, to do this you have to learn 1 single command:
>
How this is used is:
./configure > /home/user/configure.output
And all output from the ./configure process will be copied to the text file in /home/user/configure.output
Now you only have to copy that file to your floppy/windows partition/CDRW instead of having to figure out how to copy and paste many many lines from your terminal to a text file. You can do that with anything:
make > /home/user/make.output
You can name the text file anything you'd like:
make > /home/user/toadstool
If you want. The naming convention really isn't important, however for ease of use on windows you might consider the extension .txt so:
make > /home/user/make.txt
Might be what you want to use so that Notepad or Wordpad can open it up easier.
FYI: /home/user is just an example, replace that with your current user's home directory, so if your user is named "pablo" then your home directory would most likely be:
/home/pablo
So use that instead of "/home/user" in my examples.
Cool
