With that bit of wisdom in mind, I stand corrected, and here is the error message I
get:
# find / -name gcc | sed -n '/gcc$/p'
find: /mnt/floppy: Input/output error
find: /mnt/cdrom: Input/output error
#
(returns the I/o errors and then returns a prompt)
-Daniel
--- "D. Joe Anderson" <[EMAIL PROTECTED]> wrote:
On Wed, Sep 15, 2004 at 05:37:14PM -0500, D. Joe Anderson wrote:
> On Tue, Sep 14, 2004 at 11:03:39AM -0500, Daniel & Kim Cotter wrote:
>
> > I ran the ./configure command, and the results are about 15 lines of
> > errors, all meaning that it can't find the C compiler. I do have the
> > gcc package installed; is it possible the path to it is not listed?
>
> gcc is necessary, but rarely sufficient, to compile anything.
I should have noted this before: You should almost always just
go ahead and append the actual error messages (not pages and
pages of them, but you're only talking about 15 lines) rather
than a description of them, which may involve an unwarranted
conclusion or unspoken assumption. Maybe it is just a path
error, but that seems like an odd thing to find in a stock
system.
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
--
Joe
