* Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
@ 2017-09-11 16:27 Jim Reisert AD1C
2017-09-11 16:33 ` Jim Reisert AD1C
2017-09-11 17:51 ` Achim Gratz
0 siblings, 2 replies; 5+ messages in thread
From: Jim Reisert AD1C @ 2017-09-11 16:27 UTC (permalink / raw)
To: cygwin
[-- 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
2017-09-11 16:27 Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0 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
1 sibling, 1 reply; 5+ messages in thread
From: Jim Reisert AD1C @ 2017-09-11 16:33 UTC (permalink / raw)
To: cygwin
I now realize that Net::SSLeay and LWP::Protocol::https are both
pre-compiled modules that I can download from Cygwin. But even after
re-installing LWP::Protocol::https, my Perl program still won't run:
Can't locate LWP/Protocol/https.pm in @INC (you may need to install
the LWP::Protocol::https module) (@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 .) at
../scripts/QRZ_daily.pl line 17.
I don't know why it's not finding the module, and what this has to with gcc.
--
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
2017-09-11 16:33 ` Jim Reisert AD1C
@ 2017-09-11 17:01 ` Ken Brown
0 siblings, 0 replies; 5+ messages in thread
From: Ken Brown @ 2017-09-11 17:01 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
2017-09-11 16:27 Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0 Jim Reisert AD1C
2017-09-11 16:33 ` Jim Reisert AD1C
@ 2017-09-11 17:51 ` Achim Gratz
2017-09-11 20:55 ` Jim Reisert AD1C
1 sibling, 1 reply; 5+ messages in thread
From: Achim Gratz @ 2017-09-11 17:51 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0
2017-09-11 17:51 ` Achim Gratz
@ 2017-09-11 20:55 ` Jim Reisert AD1C
0 siblings, 0 replies; 5+ messages in thread
From: Jim Reisert AD1C @ 2017-09-11 20:55 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-09-11 20:55 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-11 16:27 Problems with building Perl modules after upgrade to g++ (GCC) 6.4.0 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 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).