FWIW, I did not try to install PDL, so I did not encounter any such problems. I'm trying to keep the system clean for testing, so I didn't plan on installing anything.
On Wed, May 2, 2012 at 1:30 PM, Joel Berger <[email protected]> wrote: > Ok so this is a brand new blead, I execute `cpanm PDL`, and eventually I > get this. I have heard that the POD system has had some overhauling going > on, so perhaps this isn't unexpected. (I have the whole log if needed) > > doc_site_install: Building PDL documentation web pages ... > Image2D.pm... > Unknown option: libpods > Doc/mkhtmldoc.pl: -: invalid parameters > Died at Doc/mkhtmldoc.pl line 140, <POD> line 25. > Making HTML docs... > > Usage: Doc/mkhtmldoc.pl --help --htmlroot=<name> --infile=<name> > --outfile=<name> > --podpath=<name>:...:<name> --podroot=<name> --cachedir=<name> > --recurse --verbose --index --norecurse --noindex > > --[no]backlink - turn =head1 directives into links pointing to the top > of > the page (off by default). > --cachedir - directory for the directory cache files. > --css - stylesheet URL > --flush - flushes the directory cache. > --[no]header - produce block header/footer (default is no headers). > --help - prints this message. > --htmldir - directory for resulting HTML files. > --htmlroot - http-server base directory from which all relative > paths > in podpath stem (default is /). > --[no]index - generate an index at the top of the resulting html > (default behaviour). > --infile - filename for the pod to convert (input taken from stdin > by default). > --outfile - filename for the resulting html file (output sent to > stdout by default). > --[no]poderrors - include a POD ERRORS section in the output if there > were > any POD errors in the input (default behavior). > --podpath - colon-separated list of directories containing library > pods (empty by default). > --podroot - filesystem base directory from which all relative paths > in podpath stem (default is .). > --[no]quiet - suppress some benign warning messages (default is off). > --[no]recurse - recurse on those subdirectories listed in podpath > (default behaviour). > --title - title that will appear in resulting html file. > --[no]verbose - self-explanatory (off by default). > > at /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/Pod/Html.pm line > 445, <POD> line 25. > Pod::Html::usage('-', 'invalid parameters') called at > /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/Pod/Html.pm line 509 > Pod::Html::parse_command_line() called at > /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/Pod/Html.pm line 286 > Pod::Html::pod2html('--podpath=.', > '--podroot=/home/joel/perl5/perlbrew/perls/perl-blead/lib/site...', > '--htmldir=/home/joel/perl5/perlbrew/perls/perl-blead/lib/site...', > '--libpods=perlfaq', '--recurse', > '--infile=/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_...', > '--outfile=/home/joel/perl5/perlbrew/perls/perl-blead/lib/site...', > '--quiet') called at Doc/mkhtmldoc.pl line 250 > main::__ANON__() called at > /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/File/Find.pm line 781 > File::Find::_find_dir('HASH(0x9e8f6a0)', > '/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.15...', 18) > called at > /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/File/Find.pm line 569 > File::Find::_find_opt('HASH(0x9e8f6a0)', > '/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.15...', > '/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.15...') called > at /home/joel/perl5/perlbrew/perls/perl-blead/lib/5.15.9/File/Find.pm line > 1070 > File::Find::find('CODE(0x9b49d88)', > '/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.15...', > '/home/joel/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.15...') called > at Doc/mkhtmldoc.pl line 267 > make: *** [doc_site_install] Error 255 > -> FAIL Installing PDL failed. See /home/joel/.cpanm/build.log for details. > 7 distributions installed > > On Wed, May 2, 2012 at 11:51 AM, Chris Marshall <[email protected]>wrote: > >> The GD fails are a known problem but I don't know >> when Judd might have a chance to address them. >> If not by the next PDL release, we may need to >> revert to the 2.4.10 code. >> >> --Chris >> >> On Wed, May 2, 2012 at 12:44 PM, David Mertens <[email protected]> >> wrote: >> > On Wed, May 2, 2012 at 8:45 AM, chm <[email protected]> wrote: >> >> >> >> Thanks to the Perl Weekly, it has been reported that >> >> perl 5.16.0 is in the final steps of the release >> >> process and we need to determine any possible issues >> >> with PDL-2.4.10, PDL-2.4.10_003, and pdl git. >> >> >> >> Specifically, we need folks to test against the latest >> >> perl-5.16.0 with PDL so we can fix any bugs for a >> >> quick release to update PDL to fully support the >> >> new stable perl release. >> >> >> >> This blog entry has some thoughts for what is needed: >> >> http://rjbs.manxome.org/rubric/entry/1955 >> >> >> >> Please report any issues ASAP to the perldl or >> >> pdl-porters list and update or create any bug >> >> tickets needed. >> >> >> >> Thanks, >> >> Chris >> >> >> >> >> >> _______________________________________________ >> >> Perldl mailing list >> >> [email protected] >> >> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl >> > >> > >> > Generally speaking, on *The Latest* Perl, Ricardo's 5.16 branch, and >> Mac OSX >> > 10.7 Lion, 64-bit, everything passes. But there are some caveats. >> > >> > The latest has GD issues. Oddly enough, these issues *do not* arise with >> > 2.4.10. >> > >> > 2.4.10 issues a handful of warnings, but all the tests pass. >> > >> > I hadn't realized that GD issues were new, and I wonder if I did things >> > correctly. Let me know which text you want to see, if any. >> > >> > David >> > >> > -- >> > "Debugging is twice as hard as writing the code in the first place. >> > Therefore, if you write the code as cleverly as possible, you are, >> > by definition, not smart enough to debug it." -- Brian Kernighan >> > >> >> _______________________________________________ >> Perldl mailing list >> [email protected] >> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl >> > > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
