Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <37725933.3BA108@ece.gatech.edu> Date: Thu, 24 Jun 1999 12:13:40 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Dana Hudes CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: corrupt cygnus Perl ports References: <3 DOT 0 DOT 5 DOT 32 DOT 19990622021435 DOT 007daec0 AT bl-mail2 DOT corpeast DOT baynetworks DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 19990622100919 DOT 0081c220 AT bl-mail2 DOT corpeast DOT baynetworks DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 19990623140050 DOT 0081b260 AT bl-mail2 DOT corpeast DOT baynetworks DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dana - (copied to the cygwin list, because the info is probably of general interest. Hope that's okay) > Managed to get a valid file and set it up. Good. It wasn't supposed to be that hard... :-) > Running perl -MCPAN -eshell > is not going smooth. IO::Socket is having trouble, libnet is hanging in the > middle. Okay, I think I know what this is. If you check the documentation (the README is available from http://cygutils.netpedia.net/perl/README.cygwin32-v1.4.1) and search for io_sock.t, you'll find that there was a problem with it. We hacked the test so that the build would go smoothly, since without this hack, the make test / perl harness *hangs* rather than reporting a failure. Unfortunately, this means that there is no warning to the unsuspecting user that io_sock doesn't work properly, unless you read the documentation pretty thoroughly. The problem is that "fork"s don't work with dlls in cygwin. Yet. See the recent thread "B20.1: Fork bug (Win95)" and an older thread "fork + dlls". Hopefully this bug, which is a cygwin problem and not a perl problem, will be fixed in B21. > ReadLine gets an uninitialized value error, so does Ext_MM > (makemaker?) > I don't understand this. But that's just because I'm (a) not a programmer, and (b) a verifiable, card-carrying Perl newbie. How I ended up "maintaining" the cygwin port of perl, I'll never figure out. I guess it's just because I'm good at collecting other people's work and packaging it up nicely. :-) --Chuck -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com