in reply to Re^2: sv_upgrade error
in thread sv_upgrade error

Yes, they updated to 5.10.0 over the summer - broke my code on there only insofaras I had to recompile the CPAN modules I was using due to the binary incompatibilities. However, to answer the question, then:

$ perl -MText::CSV_XS -le 'print $Text::CSV_XS::VERSION' 0.52
Looks like the one on DreamHost is somewhat dated. You may want to do a local install of Text::CSV_XS in that case. Thus far, I've not hit into any similar issue with my DBD::CSV usage, as I don't seem to have a newer version on my account.

Replies are listed 'Best First'.
Re^4: sv_upgrade error
by wrinkles (Pilgrim) on Nov 14, 2010 at 06:27 UTC
    So I upgraded Text::CSV (and Text::CSV_XS)
    $ perl -MText::CSV -e 'print "$Text::CSV::VERSION\n"' 1.06 $ eval $(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib) $ perl -MText::CSV -e 'print "$Text::CSV::VERSION\n"' 1.20
    And I'm getting somewhere, now I'm seeing a new error:
    EHR - getline_hr () called before column_names () at myscript.pl line + 676
    however I believe I called column_names:
    # declare column names for getline_hr $csv->column_names($csv->getline($csv_fh)); # Build Array of HashRefs my @buttons; while (my $row = $csv->getline_hr($csv_fh)) { push(@buttons, $row) unless ($. == 1); }
      OK I think I see the problem. getline IS called before column_names:
      $csv->column_names($csv->getline($csv_fh));
      Now to fix it...
        Nope, that's not it. The error is about getline_hr not getline. :(
      Make sure that getline was successful

      As of Text-CSV_XS version 0.71, you can pass the auto_diag => 1 attribute to the new () constructor (actually already in version 0.66, but in 0.71 it was fully functional. For Text::CSV these were versions 1.14 and 1.17), and all diagnostics will be automatic.


      Enjoy, Have FUN! H.Merijn
Re^4: sv_upgrade error
by ikegami (Patriarch) on Nov 14, 2010 at 05:41 UTC

    broke my code on there only insofaras I had to recompile the CPAN modules I was using due to the binary incompatibilities

    That made me wonder why INSTALL_BASE is recommended over PREFIX. Using the latter, XS modules would go missing rather than become invalid, and you could actually have multiple perl installs using the same lib dir (which is good since they all use the same ENV var to locate the lib dir).

    I just use perlbrew now.