I finally got a chance to compile some packages, but I don't know about gcc default x86. Do I put packagename-i486-1.tgz or do I put the x86 for my processor(i686)?

it doesn't really matter. Both should work, as it is the same architecture.
The x86 (hence the name) can stand for 386,486 or 686 (pentium, AMD athlon and such processors).

I know it doesn't really matter. It's just a matter of curiosity and wanting to have my packages labled correctly.(step 1 on my road to learning slack package management)

it might just be a bit optimized for the architecture. if you have i686, then if you can find i686 use that, otherwise any of the x86 types will fit.

Right. I want to know if the packages that I compile on my machine are bit optimized for my architecture, or the origional architecture that the slackware gcc was compiled for(i486).

The optimization can be set using FLAGS or editing the /etc/make.conf file. Search the web for both. What you will set, will be how the stuff is compiled.

Thank you very much

Make has a conf file!?!
Maybe there's other things that can be tweaked in it...

I've seen FLAGS in some of the compiler messages so I'll have to check the make files and do some research

IIRC /etc/make.conf is a gentoo thing.


man make says squat about it, so i'd think as much.

You may want to take a look at this little HOWTO GCC Myths and Facts. You can also get "technical" with the GCC documentation Intel 386 and AMD x86-64 Options.

Basically you can set a "general" cpu type with the following CFLAG variable:
"-march=i686"
This will compile the program for all 686 processors, this includes Athlons as well.

If you have a Pentium IV CPU you can further optimize with this:
"-march=i686 -mcpu=pentium4"
This is the same as above, but it "turns on" special features that are avialable to the Pentium 4.

The way that Pat V compiles most, not all but most, of the software for Slackware is to use:
"-march=i486 -mcpu=i686"
This allows for the most compatibility with nearly every processor out there with the special features that will be used if the package is installed on a 686 processor.

HTH,
MMYoung

Thanks for the links! The one at freshmeat.net was really helpful. I guess I'll have to take a closer look at my makefiles from now on. I cant wait to finish the GCC manual! I've also starting downloading the other GNU tools manuals to see what wealth of information they hide.