[Module::Build] Re: Smoke [5.9.4] 27656 FAIL(F) MSWin32 WinXP/.Net SP2 (x86/2 cpu)

[Randy W. S. <ml...@th...>]

Randy W. Sims wrote:
> Steve Hay wrote:
>> Builds fine for me @ 27707.  I would guess it's maybe a Borland setup 
>> problem.  Did you create the *.cfg files in its Bin/ directory?
> 
> Yeah, my bad. I remember needing to do that before, now that you've 
> mentioned it. I skimmed through the help doc that came with the 
> compiler, but I must of missed a readme somewhere. (It's not in perl's 
> README.win32 either.)
> 
> I'll try again sometime today, hopefully.
> 
> Good news is I think I know what the problem is from the verbose output 
> you posted.

Ok, I finally got around to looking. The problem is where I suspected: 
It's the quoting of the macros VERSION & XS_VERSION. On the command line 
you can type:

  bcc32 -DVERSION=\"1.01\" test.c

But we use response files for all compilers on Windows (GCC, BCC, & 
MSVC), and the response files seem to require a different quoting syntax 
that I haven't figured out yet. I've tried

-DVERSION=\"1.01\"
Error E2206 test.c 7: Illegal character '\' (0x5c) in function main
Error E2206 test.c 7: Illegal character '\' (0x5c) in function main
Error E2060 test.c 7: Illegal use of floating point in function main
*** 3 errors in Compile ***

-DVERSION="1.01"
Error E2060 test.c 7: Illegal use of floating point in function main
*** 1 errors in Compile ***

And several other variations that always results in one of the errors above.

I've posted on one of the borland newsgroups see if anyone can help 
there. If I can't find a quoting solution, I guess I can move macros of 
the key=value form back onto the commandline, for bcc.

Randy.

The test snippets I used are of the form:

test.c:
----------8<----------
#include <stdio.h>

int main()
{
   char *v;
   v = VERSION;
   printf("%s\n", v);
   return 0;
}
----------8<----------

test.rsp:
----------8<----------
-DVERSION=\"1.01\"
----------8<----------

With the command:

   bcc32 @test.rsp test.c