From: Jim Reisert AD1C <jjreisert@alum.mit.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 20:55:00 -0000 [thread overview]
Message-ID: <CAK-n8j7T87K9bNFsaSyC4NRzAQg0_+BoH41e_dw-fWevCNOhPg@mail.gmail.com> (raw)
In-Reply-To: <87o9qhw2cu.fsf@Rainer.invalid>
On Mon, Sep 11, 2017 at 11:51 AM, Achim Gratz wrote:
> Unless you know what you're doing and can navigate the inevitable
> obstacles, do not use cpan on Cygwin.
I have been building Perl packages for years without problems. I use
WWW::Mechanize in several programs, and it has a lot of
pre-requisites.
>> SSLeay.xs:163:25: fatal error: openssl/err.h: No such file or directory
>> #include <openssl/err.h>
>
> The most likely reason is that you do not have the *-devel package for
> openssl installed.
Missed that, thanks!
I don't know why Cygwin "upgraded" me from Perl 5.22 to Perl 5.24. I
am building a new Cygwin installation from scratch (via setup) and it
has Perl 5.22 (as expected) and gcc 6.4. I seem to remember this
problem happening in the not-too-distant past when gcc 6.x was
experimental, so I probably picked up the experimantal Perl 5.24 as
well. I tried to roll back Perl from 5.24 -> 5.22 in my existing
Cygwin (non-experimental) installation but "perl --version" still
returned version 5.24
Anyway, I'll have a clean installation soon, I hope.
- Jim
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
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
prev parent reply other threads:[~2017-09-11 20:55 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
2017-09-11 17:51 ` Achim Gratz
2017-09-11 20:55 ` Jim Reisert AD1C [this message]
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=CAK-n8j7T87K9bNFsaSyC4NRzAQg0_+BoH41e_dw-fWevCNOhPg@mail.gmail.com \
--to=jjreisert@alum.mit.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).