script will fail, god not found.

Getting back on topic...

I'm pretty sure studio.h and crt1.o are part of glibc. You don't need the glibc headers to run a linux system, only to compile c progs in a linux system. Actually, those headers are part of the kernel headers that glibc was compiled against iirc. Not to be confused with the headers for the running kernel you need in order to compile a kernel modules. Mandy and RH call that part of glibc glibc-dev or something like that. Never used slack so I don't know what they call it, went right to LFS/BLFS from rh myself.

Looks like stdio.h is already installed - but it's stuck in the following directory..

/usr/include/bits/stdio.h

How to i tell GCC that this is where the file is

stdio.h should also be in /usr/include/stdio.h . At least my system has it in both places. And I suspect they are not the same file. Just checked, they're not. /usr/include/stdio.h 22kb vs 5kb for /usr/include/bits/stdio.h. studio.h is a very basic include file. #include <stdio.h> is one of the first things you learn in c. If gcc can't find that then something is _really_ broken. My best guess is an incompletely installed developement system, most likely the glibc libraries are installed but not the glibc headers. Many distros split into runtime and "developement" packages on glibc and the kernel source. I think that's what's going on here.

FYI, Most of the gcc configuration is in /usr/lib/gcc-lib/<version>/specs but trust me, you _don't_ want to mess around in there.

\\Mod Note: Please do not insult each other's beliefs - and stay on topic. Thank you.