public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
Date: Mon, 11 Sep 2017 16:27:00 -0000	[thread overview]
Message-ID: <CAK-n8j6ThJ=QVjznRbV-x4aUq=AgojDd11i8ir_r-MBo1MyT4g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]

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 would roll back to GCC 5.x but that doesn't appear to be an option in Setup.

# cpan install Net::SSLeay

Running Mkbootstrap for Net::SSLeay ()
chmod 644 "SSLeay.bs"
"/usr/bin/perl.exe" "-Iinc" "/usr/lib/perl5/5.24/ExtUtils/xsubpp"
-typemap "/usr/lib/perl5/5.24/ExtUtils/typemap" -typemap "typemap"
SSLeay.xs > SSLeay.xsc && mv SSLeay.xsc SSLeay.c
gcc -c   -DPERL_USE_SAFE_PUTENV -D_GNU_SOURCE -U__STRICT_ANSI__ -ggdb
-O2 -pipe -Wimplicit-function-declaration
-fdebug-prefix-map=/mnt/share/maint/perl.x86_64/build=/usr/src/debug/perl-5.24.1-1
-fdebug-prefix-map=/mnt/share/maint/perl.x86_64/src/perl-5.24.1=/usr/src/debug/perl-5.24.1-1
-fwrapv -fno-strict-aliasing -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -DUSEIMPORTLIB -O3   -DVERSION=\"1.81\"
-DXS_VERSION=\"1.81\"
"-I/usr/lib/perl5/5.24/x86_64-cygwin-threads/CORE"   SSLeay.c
SSLeay.xs:163:25: fatal error: openssl/err.h: No such file or directory
 #include <openssl/err.h>
                         ^
compilation terminated.
make: *** [Makefile:357: SSLeay.o] Error 1
  MIKEM/Net-SSLeay-1.81.tar.gz
  /usr/bin/make -- NOT OK

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 58500 bytes --]

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
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

             reply	other threads:[~2017-09-11 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 16:27 Jim Reisert AD1C [this message]
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

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-n8j6ThJ=QVjznRbV-x4aUq=AgojDd11i8ir_r-MBo1MyT4g@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).