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

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

Replies are listed 'Best First'.
Re^10: trying to build PAR-Packer-1.002
by syphilis (Archbishop) on Mar 19, 2010 at 10:41 UTC
    I'd like to try other modules, how can I find out which ones require the 'C' compiler?

    Any module whose source contains .xs files will require the C compiler. However, the particular failure here seems to be related to the building of an executable (par.exe) using g++.exe ... and I don't know of any modules OTTOMH that will do the same.

    they suggested I had a corrupt installation of MingW

    That's what it looks to me, too ... but we haven't yet managed to uncorrupt it.

    If you can be bothered, provide me with a copy'n'paste of the outputs of the following:
    1) gcc -v
    2) g++ -v
    3) dmake -V
    and I'll make sure that I get the exact same packages. Maybe then I'll be able to reproduce the failure ... and if I can do that, then we should be able to come up with a fix.

    However, I'm about to go to bed now, and I won't be back around on perlmonks for approximately another 20 hours ... so there's no real hurry to provide those details :-)

    Cheers,
    Rob
[reply]
      Hi Rob,

      I've ran those commands, please let me know if that sheds any light on it.

      C:\Perl>gcc -v
Reading specs from C:/Perl/site/lib/auto/MinGW/bin/../lib/gcc/mingw32/
+3.4.5/specs
Configured with: ../gcc-3.4.5-20060117-3/configure --with-gcc --with-g
+nu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw -
+-enable-threads --disable-nls --enable-languages=c,c++,f77,ada,objc,j
+ava --disable-win32-registry --disable-shared --enable-sjlj-exception
+s --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boe
+hm --disable-libgcj-debug --enable-interpreter --enable-hash-synchron
+ization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw-vista special r3)

C:\Perl>g++ -v
Reading specs from C:/Perl/site/lib/auto/MinGW/bin/../lib/gcc/mingw32/
+3.4.5/specs
Configured with: ../gcc-3.4.5-20060117-3/configure --with-gcc --with-g
+nu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw -
+-enable-threads --disable-nls --enable-languages=c,c++,f77,ada,objc,j
+ava --disable-win32-registry --disable-shared --enable-sjlj-exception
+s --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boe
+hm --disable-libgcj-debug --enable-interpreter --enable-hash-synchron
+ization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw-vista special r3)

C:\Perl>dmake -V
dmake.exe - Version 4.11-20080107-SHAY (Windows / MS Visual C++)
Copyright (c) 1990,...,1997 by WTI Corp.

Default Configuration:
        MAXLINELENGTH := 32766
        MAXPROCESSLIMIT := 4
        MAXPROCESS := 1
        .IMPORT .IGNORE: DMAKEROOT
        .MAKEFILES : makefile.mk makefile
        .SOURCE    : .NULL
        DMAKEROOT *= $(ABSMAKECMD:d)startup
        MAKESTARTUP := $(DMAKEROOT)\startup.mk

Please read the NEWS file for the latest release notes.

C:\Perl>

      [download]
      Thanks again

      Richard.

[reply]
[d/l]
        Groan ... those are the exact same versions that I have. And I'm running build 1007, too. It's therefore rather hard to understand how it could be building for me, but not for you.

        If you like, try building it again - but this time, unpack the source to some location that's completely outside of the C:/Perl tree - say, C:/mybuild. Then 'cd' to C:/mybuild/PAR-Packer-1.002 and run 'perl Makefile.PL' followed by 'dmake test'. If the same failure occurs, 'cd' to C:/mybuild/PAR-Packer-1.002/myldr and enter:

        C:\Perl\site\bin\g++.exe main.o my_par_pl.o -L"C:\Perl\lib\CORE" C:\Perl\lib\CORE\perl510.lib -o par.exe

        If, by some chance, that succeeds (in which case there will be no output at all) then do a 'cd ..' to get back to the C:/mybuild/PAR-Packer-1.002 folder and then re-run 'dmake test'.

        I'm really clutching at straws here - as that's all there seems to be to grab hold of. And I'm probably just wasting your time, for which I apologise.

        Cheers,
        Rob
[reply]

In Section Seekers of Perl Wisdom