This is the mail archive of the cygwin-talk@cygwin.com mailing list for the cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.12-1: ld (make) Error while compiling


On Wed, Dec 15, 2004 at 11:21:04AM -0000, Dave Korn wrote:
>> -----Original Message-----
>> From: cygwin-talk-owner On Behalf Of Dave Korn
>> Sent: 14 December 2004 15:38
>
>>Heh, that's why I asked "prasanna hegde" to post his cygcheck.  I
>>wanted to publicly mock him when his UID/home path/environment vars
>>revealed his poor attempt at socking-up!
>
>LOL.  Ask and ye shall receive.  :) Stand by for entertaining
>reactions!

As usual, the solution boils down to the OP just spending thirty seconds
actually *looking* at the problem.

Given the number of pebbles in the road that people in the cygwin
mailing list consider to be insurmountable obstacles, I really shudder
to think about the software that's making it out into the real world.
A large percentage of mainstream software must be full of mispeceptions
and unnecessary workarounds.

Look at the insight mailing list.  People who *want a debugger* are
completely stymied by C syntax errors they encounter when trying to
build the debugger.  That makes me wonder what in the world they're
going to do with a debugger.  Wouldn't they also be blown away by the
first SEGV they hit or the first actual bug in their software?

I can envision the solutions many of these people resort to for fixing
problems:

"Oh.  i is supposed to be 47 here and it's 48, so I'll just
subtract 1."

"Oh.  I got a SEGV dereferencing ptr.  I wonder how that happened.  Oh
well.  I'll just add a 'if (ptr)'.  That should fix it."

"Oh.  I'm getting a syntax error and no one on the cygwin list will help
me.  Let's see if #if 0/#endif works.  Yep.  It does."

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]