| Summary: | dev-perl/Net-DNS-0.810.0 Bareword "Errno::EINVAL" not allowed while "strict subs" in use at /usr/lib64/perl5/5.20.2/x86_64-linux/IO/Socket.pm line 135 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | darkbasic <darkbasic> |
| Component: | [OLD] Library | Assignee: | Gentoo Perl team <perl> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gem, gentoo |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
darkbasic
2015-12-17 20:23:18 UTC
Created attachment 419528 [details]
build.log
I had the same problem, but after reading this (http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2015-April/070114.html) I decided to upgrade to Perl 5.22.1, now the "errno" problem is gone. Everything seems to be running fine. (In reply to Ian from comment #2) > I had the same problem, but after reading this > (http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2015-April/070114. > html) I decided to upgrade to Perl 5.22.1, now the "errno" problem is gone. > Everything seems to be running fine. Same problem here. When I looked at going to unstable Perl 5.22.1 it seemed like I would need to keyword every perl package, so I did not do that... (In reply to Gary E. Miller from comment #3) > (In reply to Ian from comment #2) > > I had the same problem, but after reading this > > (http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2015-April/070114. > > html) I decided to upgrade to Perl 5.22.1, now the "errno" problem is gone. > > Everything seems to be running fine. > > Same problem here. When I looked at going to unstable Perl 5.22.1 it seemed > like I would need to keyword every perl package, so I did not do that... You can put this in package.accept_keywords to upgrade perl to ~arch: dev-lang/perl virtual/perl-* perl-core/* Alternatively, just upgrade to =dev-lang/perl-5.20.0-r1 (which has the gcc-5 fixes). (In reply to Andreas K. Hüttel from comment #4) > You can put this in package.accept_keywords to upgrade perl to ~arch: > > dev-lang/perl > virtual/perl-* > perl-core/* I could, but I find that the rabbit hole can get real deep once I try to maintain a 1/2 stable and 1/2 unstable system. I keep my production systems on a much stable as possible. > Alternatively, just upgrade to > > =dev-lang/perl-5.20.0-r1 I am on stable 5.20.2, so that is a downgrade. And it is no longer in portage: backup nagios-check_sip-1.2 # eix dev-lang/perl [I] dev-lang/perl Available versions: 5.20.2(0/5.20) ~5.20.2-r1(0/5.20) ~5.22.0(0/5.22) ~5.22.1(0/5.22) {berkdb debug doc gdbm ithreads} > (which has the gcc-5 fixes). 5.20.2-r1 did the trick. Thanks for the hint. Closing this since 5.22.2 is going stable now. |
