On 2017-11-15, Stuart Henderson <s...@spacehopper.org> wrote: > On 2017-11-15, Alceu Rodrigues de Freitas Junior <glasswal...@yahoo.com.br> > wrote: >> Hello folks, >> >> I'm struggling to get installed the module PerlIO::eol by downloding it >> from CPAN and installing it. >> >> I tried with both the standard perl in OpenBSD 6.1 and also one that I >> compiled with perlbrew, but the results are the same (after the classic >> "perl Makefile.PL; make"): >> >> bash-4.4$ prove -l -m -v t/1-basic.t >> t/1-basic.t .. >> 1..23 >> not ok 1 - use PerlIO::eol; >> # Failed test 'use PerlIO::eol;' >> # at t/1-basic.t line 4. >> # Tried to use 'PerlIO::eol'. >> # Error: Can't locate loadable object for module PerlIO::eol in >> @INC (@INC contains: /home/vagrant/.cpan/build/PerlIO-eol-0.16-1/lib >> /home/vagrant/perl5/perlbrew/perls/perl-5.26.1/lib/site_perl/5.26.1/OpenBSD.amd64-openbsd >> >> /home/vagrant/perl5/perlbrew/perls/perl-5.26.1/lib/site_perl/5.26.1 >> /home/vagrant/perl5/perlbrew/perls/perl-5.26.1/lib/5.26.1/OpenBSD.amd64-openbsd >> >> /home/vagrant/perl5/perlbrew/perls/perl-5.26.1/lib/5.26.1) at >> t/1-basic.t line 4. >> # Compilation failed in require at t/1-basic.t line 4. >> # BEGIN failed--compilation aborted at t/1-basic.t line 4. >> Bareword "CR" not allowed while "strict subs" in use at t/1-basic.t line 6. >> Bareword "LF" not allowed while "strict subs" in use at t/1-basic.t line 6. >> Bareword "CRLF" not allowed while "strict subs" in use at t/1-basic.t >> line 6. >> Execution of t/1-basic.t aborted due to compilation errors. >> # Looks like your test exited with 255 just after 1. >> Dubious, test returned 255 (wstat 65280, 0xff00) >> Failed 23/23 subtests >> >> Test Summary Report >> ------------------- >> t/1-basic.t (Wstat: 65280 Tests: 1 Failed: 1) >> Failed test: 1 >> Non-zero exit status: 255 >> Parse errors: Bad plan. You planned 23 tests but ran 1. >> Files=1, Tests=1, 0 wallclock secs ( 0.02 usr 0.04 sys + 0.04 cusr >> 0.06 csys = 0.16 CPU) >> Result: FAIL >> bash-4.4$ >> >> I even tried to export LD_LIBRARY_PATH to the current directory, didn't >> work either. >> >> In the past, I had problems with libs dependencies because installing >> them through pkg_add were putting them over /usr/local/lib, and libpth >> variable in Perl was not searching over there: >> >> -bash-4.4$ perl -v | head -2 >> >> This is perl 5, version 24, subversion 1 (v5.24.1) built for amd64-openbsd >> -bash-4.4$ perl -V | grep libpth >> libpth=/usr/lib /usr/lib >> >> But I don't think that's the case here since the object I'm trying to >> load is on my current directory: >> >> bash-4.4$ ls >> Changes LICENSE~ META.json MYMETA.yml README >> dist.ini eol.c eol.xs lib t >> Changes~ MANIFEST META.yml Makefile README~ >> dist.ini~ eol.h eol.xs~ perl.core write.h >> LICENSE MANIFEST.SKIP MYMETA.json Makefile.PL blib >> eol.bs eol.o fill.h pm_to_blib xt >> >> The core file over there didn't gave any hints when using "gdb -c" with it. >> >> Thanks! >> Alceu >> >> > > If I make a port using the normal ports framework and try it on -current, > I get this, which is a bit further but not all the way : > > 1..23 > ok 1 - use PerlIO::eol; > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 - open for read > Failed 17/23 subtests > > Test Summary Report > ------------------- > t/1-basic.t (Wstat: 134 Tests: 6 Failed: 0) > Non-zero wait status: 134 > Parse errors: Bad plan. You planned 23 tests but ran 6. > Files=1, Tests=6, 0 wallclock secs ( 0.01 usr 0.04 sys + 0.03 cusr 0.03 > csys = 0.11 CPU) > Result: FAIL > > >
Ha. I didn't notice before I wrote a local port, but there's already a port in the tree. So actually you should just be able to use "pkg_add p5-PerlIO-eol". In general: use the OS packages, don't try and mix with cpan. In most cases it's easier to write a port than deal with the mess that you'll end up in by using two different/conflicting package systems (i.e. OpenBSD's usual one and CPAN).
