in reply to Re^5: trying to build PAR-Packer-1.002
in thread trying to build PAR-Packer-1.002

The idea of installing the latest binutils was just to update the "binutils" component of your MinGW compiler - since that seems to be the component that's making all the unwanted noise. Now that you've removed all of MinGW, you'll need to do more than just install the binutils package.

Not to worry ... just run 'ppm remove MinGW' then 'ppm install MinGW' and then unpack binutils-2.20.1 to the C:/Perl/site/lib/auto/MinGW folder. That will overwrite the existing binutils-2.19.1 files with the binutils-2.20.1 files. Then see what happens ... I'm not all that confident it will solve the problem, but it's one thing to try.

What version of perl are you running ? - the output of perl -v (that's lower case 'v') will tell us all we need to know. If you're using an older build of ActivePerl, there could be some bug there that's preventing the build. If you're running an older 5.8.x build of ActivePerl, you could try upgrading by installing build 827 over the top of it. For older 5.10.x builds, install build 1007 over the top.

You should find a file named dmake.exe in both C:/Perl/site/bin and C:/Perl/site/lib/auto/dmake. If that's not the case then you need to ppm install it again. (You don't want 'make'.)

Cheers,
Rob

Replies are listed 'Best First'.
Re^7: trying to build PAR-Packer-1.002
by rich_d_thomas (Sexton) on Mar 18, 2010 at 15:25 UTC
    Hi Rob,

    Thanks for your reply.

    I have removed and re-installed MinGW and then overwrote the C:/Perl/site/lib/auto/MinGW files with those in the binutils tar file. Unfortunately, this gave me the same result.

    I am running PERL v5.10.1 build 1007 [291969] provided by ActiveState

    I do have dmake.exe in those two locations, here are the file properties of it in those locations.:

    Directory of C:\Perl\site\bin 18/03/2010 15:01 24,576 dmake.exe Directory of C:\Perl\site\lib\auto\dmake 18/03/2010 15:00 155,648 dmake.exe

    Is there anything else you can suggest I look at please?

    Thanks, Richard.

      Sorry - I'm completely stumped.
      I guess it wouldn't hurt to check that your g++ is basically functional. Try building this script:
      // try.cpp // #include <iostream> int main(void) { printf("Hello World"); return 0; }
      Build by running 'g++ -o try.exe try.cpp'. Even if that *doesn't* work, I would be unsure what to make of it :-)
      Are there any other modules you've been unable to build because of similar errors ?

      Only other thing I can think of is to try posting to the PAR mailing list - perhaps someone there has come across this before and knows what's needed.

      Cheers,
      Rob
        Hi Rob,

        Thanks for that.

        I was able to build and run try.cpp successfully.

        I'd like to try other modules, how can I find out which ones require the 'C' compiler? as I want to build a module that has the same compiler requirements as PAR-Packer

        I have been in dialogle with CPAN before I came to perlmonks and they suggested I had a corrupt installation of MingW, which I re-installed, but still had the problem

        CPAN said that the files mentioned in the error messages (C:\Perl\site\lib\auto\MinGW\lib\libmsvcrt.a) were installed by MingW and have no connection to PAR and PAR::Packer.

        Please could you let me know of an alternative package I can try to build

        Thanks

        Richard