Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3FD03C8A.2040202@tlinx.org> Date: Fri, 05 Dec 2003 00:06:34 -0800 From: linda w User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Joaquin Subject: Re: Cygwin port of Perl broken on Win32? Or does Cygwin not run on win32? References: <000201c3baf4$3650aff0$c901a8c0 AT macross> In-Reply-To: <000201c3baf4$3650aff0$c901a8c0@macross> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I've always wanted to put cygwin tools *first* in my path before win32 tools since in some cases, there are hidden win32 tools that obscure well known *nix tools, like 'find' (being a primitive file string search). Do you actually install both Perl installs? I'm still running on a laptop for my main desktop...not having the best of luck these days since Dell decided to go middle-ware-only dealer and not go for cutting edge HW in business capable computers (they have their consumer line of Wide-screen laptops, incompatible with most monitors, making them unsuitable for business, but make their business sized laptops incompatible with any docking station -- also incompatible with business usage -- forcing you to use lattitudes where you pay $1000 more for less features. Marketing poopoo all over customers -- like their customer support -- business customers will get support personel who can speak english, but home customers still get sexist thick accent Indians who only know how to read a script and "act" real polite (it's the left over Britsh influence) while telling you to * off. It took me 10 months to solve what should have been a simple 3 week problem because they don't talk to each other on each side of the ocean and the Indian side has no authority to do anything, but the american side that has authority won't talk with customers, so you go around in circles for 10 months to fix screwed up orders that used to be fixable in 3 weeks. It's an attempt to tire out the customer because Indians can talk on the phone for hours without really saying or accomplishing anything and get paid, per year about the cost of 2-3 machines, so it's very cost effective to route customer problem calls to India where all but the most diehard customers will just give up. It was only the possibility of losing large business customers that got them special treatment and the ability to contact US support centers (which they'll have to restaff, most likely with ex employees hired back as contractors so Dell won't have to pay benefits. I hear they took business management courses from Microsoft on how to \detain\ the best without really paying for them. :-/ Joaquin wrote: >I just always use non-Cygwin tools first before Cygwin ports. >Thus, for Perl, I use the ActiveState Perl in my path ahead of the >Cygwin perl. I also do the same for other things like Apache. > > > >>-----Original Message----- >>From: cygwin-owner AT cygwin DOT com >>[mailto:cygwin-owner AT cygwin DOT com] On Behalf Of linda w >>Sent: Wednesday, December 03, 2003 2:52 PM >>To: cygwin AT cygwin DOT com >>Subject: Cygwin port of Perl broken on Win32? Or does Cygwin >>not run on win32? >> >> >>I was told this is a problem specific to Cygwin -- that >>Cygwin believes it isn't runing on a Win platform. Is this >>true? I knowt he goal is to >>provide >>posix compatibility, but that doesn't mean it has to strive >>for windows incompatibility unless it breaks posix >>compatibility ...no? yes? maybe? >> >>-linda >> >>linda w wrote: >> >> >> >>> I'm trying to run a program that needs Registry.pm. I >>> >>> >>pull it down >> >> >>>as part of Win32::Registry, but when I try to 'make' it, it fails: >>> >>>... >>>Writing Makefile for Win32::ODBC >>>Checking if your kit is complete... >>>Looks good >>>Processing hints file hints/cygwin.pl >>>Note (probably harmless): No library found for -lole32 >>>Note (probably harmless): No library found for -loleaut32 Note >>>(probably harmless): No library found for -luuid Note (probably >>>harmless): No library found for -lmsvcrt40 Writing Makefile for >>>Win32::OLE Checking if your kit is complete... >>>Looks good >>>Writing Makefile for Win32::PerfLib >>>Checking if your kit is complete... >>>Looks good >>>Writing Makefile for Win32::Pipe >>>ERROR from evaluation of >>>//ishtar/share/CPAN/build-win/libwin32-0.191/Process/Ma >>>kefile.PL: Undefined subroutine &Win32::IsWinNT called at >>>./Makefile.PL line 4. >>> >>>Anyone have any ideas on why this is breaking or how to make this >>>work? Is >>>it something broken in the cygwin "port", of perl, on Win32? >>> >>>Thanks! >>>Linda W. >>> >>> >>> >>>-- >>>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/ >>> >>> >>> >> >>-- >>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/ >> >> >> >> >> > > > >-- >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/ > > > -- 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/