Re^2: Spreadsheet::WriteExcel and Cava packager

Replies are listed 'Best First'.
Re^3: Spreadsheet::WriteExcel and Cava packager by markwx (Acolyte) on Apr 19, 2011 at 09:00 UTC
Hi, I'm part of Cava development. Why not post to the Cava help list? Anyhow, if you run your exec in diagnostics mode it should tell you exactly where it failed. It appears to be failing during POSIX AutoLoad. Have you edited your POSIX module or autoload files locally? I have no problem building a script with Spreadsheet::WriteExcel / POSIX? Have you tried incrementing the release number?	[reply]
Re^4: Spreadsheet::WriteExcel and Cava packager by Anonymous Monk on Apr 19, 2011 at 13:39 UTC
Hello, I haven't changed anything in POSIX or autoload and I tried to run the executable in diagnostics mode but the error message was identical to the one posted by me above. What do you mean by increasing the release number?	[reply]
Re^5: Spreadsheet::WriteExcel and Cava packager by markwx (Acolyte) on Apr 19, 2011 at 23:44 UTC
Hi Increasing the release number - that would ensure that if you were compressing any files they would get extracted to a different place. I thought maybe there was some problem with overwriting a previous version's temp files. You have a four digit version number. The release number is the third digit. Increasing it guarantees a different temp path. It would be nice to repeat your problem so it can be fixed. If you start your app from the 'diagnostics and tests' page and check the box for 'verbose output', you will see the order of files loaded. If you were to post the output it would help in tracking down the issue. Check the Cava site on support page or the app documentation for a support email address if you don't want to post the output to a list.	[reply]
Re^6: Spreadsheet::WriteExcel and Cava packager by samuelalfred (Sexton) on Apr 20, 2011 at 12:18 UTC
Re^3: Spreadsheet::WriteExcel and Cava packager by Anonymous Monk on Apr 19, 2011 at 07:31 UTC
$ perl -le "binmode STDOUT; print chr($_) for 0 .. 43" > notperl.pl $ perl notperl.pl Unrecognized character \x01; marked by <-- HERE after <-- HERE near co +lumn 1 at notperl.pl line 2. $ perl -Mdiagnostics notperl.pl Unrecognized character \x01; marked by <-- HERE after <-- HERE near co +lumn 1 at notperl.pl line 2 (#1) (F) The Perl parser has no idea what to do with the specified char +acter in your Perl script (or eval) near the specified column. Perhaps +you tried to run a compressed script, a binary program, or a directory as a +Perl program. Uncaught exception from user code: Unrecognized character \x01; marked by <-- HERE after <-- HERE + near column 1 at notperl.pl line 2. at notperl.pl line 2 [download] If the source isn't mangled, then maybe a `use utf8;` is missing, or a `export LANG=...` [download] is misplaced ( something to do with locales... )	[reply] [d/l] [select]