Re: Newbie link problem: Error 1

Urs Janßen <[email protected]> wrote:

> yes, both problems you mention are configuration problems of
> your system and tins configure script warned you about that.

Where?  How?  See below.


> > I *did* look at the warnings, as you can see from the fact
> > that I pasted them into my message.  I could have pasted
> > *all* of the output, you
>
> you posted the compiler warnings, not the the ones from configure.
> configure told you:
>
> | Warning: no term-lib found, you might run into trouble later.
> | Warning: no yacc-parser found, you might run into trouble later.

I would have noticed and remembered a warning like one of these.

configure told me nothing of the kind that I can find.  I have re-run
both config and make, after downloading libncurses-devel, and attached a
copy of all of the output from running both configure and make in that
order.  The file "cmdln.txt" shows the exact commands that created the
other four files, as well as any output that was not captured in those
files.  Same problem, so far as I can tell.

Show me where that warning (or anything even remotely like it) appears
in configure's output.  Please.  I beg you.


> and that is exactly what happen after you ignored that two
> messages -

I didn't ignore any such message, unless you can point it out to me.


> > It should be obvious that I did not understand well enough
> > what I was looking at, *let alone how to fix it*, else I
> > would not have asked.  Not everyone has years of expertise
> > at running builds.
>
> of course not - and the only thing I was complaining about is
> that ppl. tend to ignore the hints (the two mentioned warnings)
> given in the instalation process and ask for help instead of
> looking at the warnings, try to fix them and if that doesn't
> work (cause one does not know what todo) ask to how to fix the
> given warning.

And what I objected to was your assumption that I made no effort to
figure out the problem on my own.  I don't make a habit of joining
mailing lists.  I value my privacy, and assume others value theirs as
well.  I wouldn't bother writing any of this if I wasn't stuck.  I'm
neither stupid nor lazy, just ignorant of unix/linux/cygwin conventions.

I do tinker with stuff on my own.  But I'm cautious, especially when I
don't understand the system well.  I don't want to take a chance of
damaging something system-wide due to my not knowing the ramifications
of some seemingly minor change I make in a script somewhere.

-- Jeff

---------------------------------------------------------------
  Keep away from people who try to belittle your ambitions.
  Small people always do that, but the really great make you
  feel that you, too, can become great. -- Samuel Clemens
---------------------------------------------------------------