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]

Richard.

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

Hi Rob

Please don't apologise for the time I am spending following your suggestions, I really appreciate the time you are spending thinking through and giving me suggestions. It should be me apologising to, you for having this weird problem that you are kindly helping me out with.

On to the results of those steps...

When I tried to make test in the newly created and unpacked C:/mybuild/PAR-Packer-1.002 folder, I got the same errors.

When I submitted the long g++ command, it did not report any errors and it had executed very quickly, having generated the following file:

20/03/2010  10:53            71,235 par.exe

So I re-did the dmake test and unfortunately got the same error.

Do you know if there is any way I can test the package that coffgen.c is in, outside of doing a full blown build of PAR-Packer?

If there is, do you think it's worth me trying that?

Thank you for all your help so far

Richard