From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
To: Dana Hudes <dhudes@BayNetworks.COM>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: corrupt cygnus Perl ports
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <37725933.3BA108@ece.gatech.edu> (raw)
Message-ID: <19990630221000.Q32q34_KNDIg9QSZ8k8vZx8hEgXQCKjb6SJ3S4zZWpk@z> (raw)
In-Reply-To: <3.0.5.32.19990623140050.0081b260@bl-mail2.corpeast.baynetworks.com>
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@sourceware.cygnus.com
next parent reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.5.32.19990622021435.007daec0@bl-mail2.corpeast.baynetworks.com>
[not found] ` <3.0.5.32.19990622100919.0081c220@bl-mail2.corpeast.baynetworks.com>
[not found] ` <3.0.5.32.19990623140050.0081b260@bl-mail2.corpeast.baynetworks.com>
1999-06-24 9:12 ` Charles S. Wilson [this message]
1999-06-30 22:10 ` Charles S. Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37725933.3BA108@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=dhudes@BayNetworks.COM \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).