RE: Can't build cygwin from CVS: configure error

["Hannu E K Nevalainen" <garbage_collector at telia dot com>]

> From: Christopher Faylor
> Sent: Sunday, October 12, 2003 12:04 AM

This is long and winding, not entirely on topic - you've been warned.

> On Sat, Oct 11, 2003 at 11:38:36PM +0200, Hannu E K Nevalainen wrote:

> > =-)  Well, eventually it did work with the root level configure.
> >The reason I aimed at that one was that the FAQ told me to go for it.
> >
> >Having instructions and "the real life situation" not match each
> other makes
> >me go nuts ;-) .
>
> Would you GIVE IT A REST for crying out loud?
>
> The instructions work.  You found a bug in CVS.  It took longer to fix
> than it should have because you spent all of your time whining about
> how bad the instructions were rather than using common sense, noticing
> the *errors* that occurred when you checked things out of cvs, and
> reporting the *errors*.

Inexperienced user, first time cvs use, loads of lines whizzing by, no error
message *at the end*; not a likely situation to generate a usable error
report.

 I'm not blaming you, somebody else nor cvs for the failure. All those
comments were _impersonal_ as I see it.

On other words; You don't need to take offense, I REALLY hope that my
writing didn't imply something in line with that.
I *do* express my frustration though, if that is so hard reading... well I
don't know what to do about that.

Once again; please don't take it so personally.

> Additionally, there is no requirement to put the sources in a specially
> named directory.  You can put them in /src.  You can put them in /bob.
>
> You can build in a subdirectory of /src.  You can build in a separate
> directory entirely.
>
> > A simple README and/or a Makefile could've helped a lot.
>
> Yeah.  A README.  Or a Makefile.  Sigh.

Sigh - yes, or even better; the FAQ stating that there should be a configure
script in the root dir after the checkout - as it depends on it beeing
there - i.e. "You should now have a /src/configure script. Run it like
this:".
 (The description also assumes that one have done "cd /"... but it isn't
stated anywhere... confusion factor increases.)
That would have made me - being a beginner - able to tell that something was
wrong, not considering cvs malfunction at this occasion.

 As a beginner I'm vulnerable to things like that - I do not have the
experience to say when something has gone wrong.
I would consider this being "a stability issue" for the FAQ/documentation.
Software that is "unstable" usually gets fixed... hint, hint ;-)
(yes I know; PTC, we've been there before)

> >I'll be investigating gdb and the possibilities with this dll.
>
> Please don't bother.  I'm asking again.  Please give it up.

 Right, I've got the picture... I have interest in the matter though, this
is the way I learn.
Once again, I'm not *trying* to get you into this mood. My style of
expressing myself, my frustration and such, seems to peck hard on your mind.
Sorry about that. I wish I could supply you with "polariod glasses" for
filtering it out.

> Go rest.
> No feedback required.  You're off the hook.  Pull out a cold one,

> kick back the recliner and go watch "Dharma and Greg".

 Yuck, that was a *real* bad one... ;-p

> Let the experts build and debug cygwin.

 You know, I really didn't expect to be to any help here... I haven't
checked but anyway; If you go back and read the postings I've made, I would
be VERY surprised if there wasn't one implication *or more* about me not
expecting to be the right person for the task (you won't see it spelled out
though).
 When someting catches my interest it's easy to get me carried along, going
in that direction though... I *like* to be in the middle of things.

 Hope this helps explain and understand that I'm not here to destroy nor
offend.

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/