Skip to main content

Solving PAR::Packer "Can't locate loadable object for module IO in @INC"

Building an executable with Strawberry Perl is successful but when actually running it (after we have renamed the c:/strawberry to c:/strawberryX so it cannot find the dependencies from the path), fails with the following errors :

" Can't locate loadable object for module IO in @INC (@INC contains: CODE(0xa1d31c
) C:\strawberry\perl\vendor\lib .) at C:/strawberry/perl/site/lib/PAR/Heavy.pm l
ine 103
Compilation failed in require at C:/strawberry/perl/lib/IO/Handle.pm line 266.
BEGIN failed--compilation aborted at C:/strawberry/perl/lib/IO/Handle.pm line 26
6.
Compilation failed in require at C:/strawberry/perl/lib/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at C:/strawberry/perl/lib/IO/Seekable.pm line
101.
Compilation failed in require at C:/strawberry/perl/lib/IO/File.pm line 133.
BEGIN failed--compilation aborted at C:/strawberry/perl/lib/IO/File.pm line 133.
Compilation failed in require at -e line 351. "

I am on WinXP SP3 ,PAR 1.002,PAR::Packer 1.009, and have tried Strawberry Perl versions 5.12.3.0,5.10.1.5,5.10.1.1 and the problem persists in all of them

perl -V reveals something strange with the backslashes:

%ENV:
   PERL_JSON_BACKEND="JSON::XS"
   PERL_YAML_BACKEND="YAML"
 @INC:
   C:/strawberry/perl/lib
   C:/strawberry/perl/site/lib
   C:\strawberry\perl\vendor\lib
   .

"C:\strawberry\perl\vendor\lib" is not consistent with the other entries

I've found id 52794 which is related to the issue although it refers to version PAR::Packer 1.001;
nevertheless I got the following line :
"if ($Config{_delim} eq '\\') { s{\\}{/}g for @inc }"
from the patch (the patch actually REMOVES this line!!) and added it to par.pl after line 540.


I also corrected Strawberry's @INC by prepending the path  "C:/strawberry/perl/vendor/lib" by setting the PERL5LIB env variable, rebuilt it and everything works fine and even tried it in machines that have no Perl installation whatsoever

It looks like Strawberry has the path messed up and needs the correct one.

Furthemore "if ($Config{_delim} eq '\\') { s{\\}{/}g for @inc }" satisfies Heavy.pm

Comments

Popular posts from this blog

Serverless JavaScript

We recently joined in an interesting two-hour long conversation about Serverless JavaScript led by Steve Faulkner of Bustle who answered questions on Bustle, the Shep framework, the mindset behind the AWS Lambda infrastructure, and related topics.

The discussion took place on the Sideway conversation-sharing platform on January 6th. Here we present the best takeaways from the session which really should be taken notice of by anyone working on AWS.

Steve Faulkner:
At Bustle we serve over 50 million unique readers per month through a "serverless" architecture based on AWS Lambda and Node.js.  Of course there are still servers but we don't manage them. This shift has allowed us to develop products faster and decreased the cost of our infrastructure. I'll answer any questions about how we made this transition and how it has worked out. I'll also discuss some of the tools and best practises including our open source framework shep

Eran Hammer:
When would you…

First Hybrid Open-Source RDBMS Powered By Hadoop and Spark

Splice Machine is a novel attempt to merge the best parts of the traditional relational database management systems and their NoSQL counterparts with distributed and in-memory computing based on Hadoop and Spark.

Traditional RDBMS find it tough when faced with massive amounts of data, which they typically handle by scaling up, albeit expensively. Another side effect of the sheer volume of data accumulating from the likes of social media and mobile devices, is that OLTP and OLAP queries carry high performance hits that subsequently have detrimental effects on real time analysis and instant decision making.

full article on i-programmer

Google's Cloud Spanner To Settle the Relational vs NoSQL Debate?

Cloud Spanner is a new proposition for database as a service that emphatically offers "Relational with NoSQL scaling". Will Google come to dominate yet another market?

Once upon a time there was only one kind of database management system, the RDBMS, "R" for relational. Despite its resilience and trustworthiness, it had its shortcomings; it did not scale well, and the relational model it served proved inadequate in the dawn of the Big Data era for handling massive amounts of schema-less, unstructured data.
For this and a few other reasons, a new breed of DBMS's emerged, one that could handle the avalanche of big data, based on the notion of the key-value pair, and doing so by scaling horizontally. But, in order to become versatile, this new breed of management systems had to forgo the safety of the ACID and the cosiness of SQL, both long term partners of the relational model. full article on i-programmer