From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
Date: Mon, 11 Sep 2017 17:01:00 -0000 [thread overview]
Message-ID: <639b67ba-3575-7cb1-0e67-6a6ecbb4ea8e@cornell.edu> (raw)
In-Reply-To: <CAK-n8j7VFdgKzRksdbqwHx+YezqX2hPw4aKvqfgqyh0Uwp1F1g@mail.gmail.com>
On 9/11/2017 12:33 PM, Jim Reisert AD1C wrote:
> @INC contains:
> /usr/lib/perl5/site_perl/5.24/x86_64-cygwin-threads
> /usr/lib/perl5/site_perl/5.24
> /usr/lib/perl5/vendor_perl/5.24/x86_64-cygwin-threads
> /usr/lib/perl5/vendor_perl/5.24
> /usr/lib/perl5/5.24/x86_64-cygwin-threads /usr/lib/perl5/5.24 .
It looks like you're using the test release of perl-5.24. But the Perl
modules in the Cygwin distro have been built for perl-5.22. If you
downgrade to perl-5.22.4-1, you should be OK.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-09-11 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 16:27 Jim Reisert AD1C
2017-09-11 16:33 ` Jim Reisert AD1C
2017-09-11 17:01 ` Ken Brown [this message]
2017-09-11 17:51 ` Achim Gratz
2017-09-11 20:55 ` Jim Reisert AD1C
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=639b67ba-3575-7cb1-0e67-6a6ecbb4ea8e@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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).