A favor from someone with XP?

NTDEV
1

I am trying to find out why my development machine, XP 32, cannot properly execute OACR/PREFast. If someone could help me I would really appreciate
it. If someone could duplicate these steps:

  1. Download and unzip the DIO driver from OSR. http://www.osronline.com/article.cfm?article=403
  2. On a 32 bit XP development machine (with the DDK, I’m using 7600.16385.1) open a build environment Win7 checked amd64.
  3. Build the driver (build -ce). It should build just fine.
  4. Wait for OACR to finish. On my machine OACR reports
    PREfast - Error processing ‘wdfdio.cpp’ : error C2371: ‘size_t’ : redefinition; different basic types (try ‘oacr log root:amd64chk’ for details)
    Warning 20051 Source Path c:\winddk\7600.16385.1\inc\crt\ Source Location crtdefs.h(457)

If instead of letting OACR run, I set up the build environment without OACR, then run PREfast by hand, I do not see the error.

Again, any help would be greatly appreciated.

2

I tried this on XP SP3 and encountered the same size_t error that you have been chasing.

Thomas F. Divine

3

This seems to be exactly because of c++, exactly what already been discussed here.
After renaming the cpp file to .c, and fixing it to compile in c mode, oacr is happy.

Regards,
– pa

4

Whew! Thanks! Thanks! Thanks!

At least I know it’s not me! So if this is due to the c++, is there some flag that can be set? The build environment seems to compile it OK…

On Sat, 15 Jan 2011 17:28:41 -0500 (EST), xxxxx@pcausa.com wrote:

I tried this on XP SP3 and encountered the same size_t error that you have been chasing.

Thomas F. Divine

5

Thanks very much!

Is there a flag that can be set to handle this?

On Sun, 16 Jan 2011 07:24:34 -0500 (EST), xxxxx@fastmail.fm wrote:

This seems to be exactly because of c++, exactly what already been discussed here.
After renaming the cpp file to .c, and fixing it to compile in c mode, oacr is happy.

Regards,
– pa

6

“Michael Wade” wrote in message
news:xxxxx@ntdev…
> Thanks very much!
> Is there a flag that can be set to handle this?

You’re welcome. A flag to handle this? Hm…
Perhaps with one like that: http://bit.ly/ftPHKs

Regards,
– pa