There are two things you want to check. Your problem is probably the second.
1. Do you have all the libraries that gcc needs to *run*? Check this with
"ldd /fullpath/gcc" replacing fullpath with the actual path.
2. Do you have all the libraries that gcc needs to *compile* and *link*
other programs? Though I've said "libraries" here, what you are more likely
to be missing are the header files that gcc needs to link in the standard
pre-compiled libraries. A closer look at the error messages you get should
tell you what header files are missing. There is probably a single, separate
rpm that has allthis stuff in it (at least I know that, on Slackware, there
is a single .tgz file for it).
Although complete reinstalls for every little thing aren't "in the Linux
spirit," adding in a gcc compiler is a pretty fundamental change, so
(especially for a relative beginner) it might be a good idea to do a full
reinstall and let the distribution maker get the details right for you.
At 05:58 PM 2/14/99 -0000, Chris Rae wrote:
.
>now gcc is at least "there" but it doesn't like compiling things much. Pages
>and pages of error messages.
>
>Am I likely to be missing some libraries which are in packages I haven't
>installed? Is there any way I can see which packages on the CD list gcc as a
>dependency which might give me an idea as to what I'm missing?
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
