From: Achim Gratz <Stromeko@nexgo.de>
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:51:00 -0000 [thread overview]
Message-ID: <87o9qhw2cu.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAK-n8j6ThJ=QVjznRbV-x4aUq=AgojDd11i8ir_r-MBo1MyT4g@mail.gmail.com> (Jim Reisert's message of "Mon, 11 Sep 2017 10:27:26 -0600")
Jim Reisert AD1C writes:
> After upgrading to g++ (GCC) 6.4.0, I am being forced to
> reload/rebuild a bunch of Perl modules that had been working fine. I
> had the same issue with GCC 6.3. One module is particularly
> troublesome. I have the openssl library installed. This is with the
> 64-bit Cygwin. I attached cygcheck.out
I don't know why that would be necessary or why the gcc update has
anything to do with it.
> # cpan install Net::SSLeay
Unless you know what you're doing and can navigate the inevitable
obstacles, do not use cpan on Cygwin.
> 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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:51 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 [this message]
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=87o9qhw2cu.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).