----- Original Message ----- From: "Daniel CESAIRE"

I try secondly to compile it from source files.

Yes, that's probably the best way to get the job done in this instance.

I use nmake.exe. It display this :
Attached is the makefile generated  Makefile.PL

However, you need to use 'dmake' - it comes with Strawberry Perl, it's what Strawberry Perl expects to use, and it's already in your path.

The Makefile that you attached is written for 'dmake' - nmake needs a different syntax, and the errors you see are the syntax errors one expects to see when 'nmake' is run on a Makefile built for 'dmake'.

Before building, I needed to have the python executable in my path and, in the Makefile.PL, I needed to change:

   $p .= "/python";
to
   $p .= "/python.exe";

Even then I couldn't get past the 'perl Makefile.PL' stage because the Makefile.PL couldn't get the information it wanted from my python.exe (version 3.1.2). I didn't persevere as I'm not personally interested in python and know nothing about it. (It's on my PC only because it was needed to build a library at some stage.)

So ... continue to try a manual build - just use 'dmake' instead of 'nmake', and let us know how you get on.

Cheers,
Rob

Reply via email to