Link errors : InterlockedBitTestAndComplement, MemoryBarrier, RtlSecureZeroMemory

Link errors : InterlockedBitTestAndComplement, MemoryBarrier, RtlSecureZeroMemory

• JeroGrav

  That is exactly what I would have thought had common.c not been written by me and contain no defintions like that of any sort
  
  common.c:
  #include <fmod.h>
  #include <fmod_errors.h>
  #include <ruby.h>
  
  void ERRCHECK(FMOD_RESULT result, const char* file, int line )
  {
  if (result != FMOD_OK)
  {
  printf("FMOD error! (%d) %s %s %d\n", result, FMOD_ErrorString(result), file, line);
  rb_raise(rb_eRuntimeError, "FMOD error! (%d) %s", result, FMOD_ErrorString(result));
  //exit(-1);
  }
  }
  
  void sound_mark(FMOD_SOUND *sound){}
  
  void sound_free(FMOD_SOUND *sound){ FMOD_Sound_Release( sound ); }
  
  void system_mark(FMOD_SYSTEM *system){}
  void system_free(FMOD_SYSTEM *system){FMOD_System_Close( system ); FMOD_System_Release( system );}
  
  void channel_mark(FMOD_CHANNEL *channel){}
  void channel_free(FMOD_CHANNEL *channel){ free( channel );}
  
  void dsp_mark( FMOD_DSP* dsp ){}
  void dsp_free( FMOD_DSP* dsp ){ FMOD_DSP_Release(dsp);}
  
  void vector_mark(FMOD_DSP *vector){}
  void vector_free(FMOD_DSP *vector){ free( vector );}
  
  void geometry_mark(FMOD_DSP *geometry){}
  void geometry_free(FMOD_GEOMETRY *geometry){FMOD_Geometry_Release( geometry );}
  
  void channelGroup_mark(FMOD_DSP *channelGroup){}
  
  void channelGroup_free(FMOD_DSP *channelGroup){free( channelGroup );}
  
  inline
  VALUE bool2val( FMOD_BOOL val )
  {
  if ( val > 0 ) return Qtrue;
  return Qfalse;
  }
  
  I really doubt ruby.h is doing it... Other programs compile on VC8 using fmod.h and fmod_errors.h work fine, so I don't think it is that.
  
  

• YoungJoe

  So after messing around, trying to compile any ruby extension that has multiple source files that reference fmod.h will fail.
  
  but fmod.h, and all files it includes, do not include any windows headers whatsoever.
  
  

• Marlin7

  
  So it looks like those functions are somehow being defined from winnt.h
  
  Part of common.i:
  #line 2719 "C:\\Program Files\\Microsoft Platform SDK\\Include\\.\\winnt.h"
  
  
  #pragma warning(push)
  #pragma warning(disable:4035 4793)
  
  BOOLEAN
  
  InterlockedBitTestAndComplement (
  LONG *Base,
  LONG Bit
  )
  {
  __asm {
  mov eax, Bit
  mov ecx, Base
  lock btc [ecx], eax
  setc al
  };
  }
  
  Which I think are being included from one of the fmod headers, but I'm not sure how to tell.
  So.. I'm really at a loss to do right now, but I'll fiddle with it and try to come up with another way to proceed, unless anyone else can think of something.
  
  

• rwilson06

  The Windows equivalent of the Unix stdc++ is probably one of the variants of the C++ runtimes - either msvcprtd.lib or libcpmt.lib.

  The rest of the error you are, as you have already realized, all Win32 functions - so it looks as if the application that you are compiling provides its own definition of these functions (in common.c) but it is also still linking against the Win32 libraries (probably kernel32.lib). This makes me suspect that the application may have been orginally developed on Win32 and these definitions were added to common.c to make it easier to port the application to Unix. Note: even though some of these functions by not be directly referenced in your code they are probably indirectly referenced by a lot other functions (some of them like _RtlSecureZeroMemory are pretty core to Win32).

  As it looks like you are porting the application back to Windows the easiest thing might be to just ignore the definition is common.c. You may find they are all under some sort of #ifdef ... #endif block and that if you set or clear a specific preprocessor definition then they will not be included in the build.

  
  
  

• ruivlessa

  I would try compiling common.c with /P or /E and take at the preprocess output - if the linker is attributing these definitions to common.obj then they have to be defined somewhere in this compiland - either that or there is another common.obj somewhere in the project or in a library referenced by the project.
  
  

• Thomas LEBRUN

  wow... After hours of working on this problem the issue seems to be in which order the headers are included.
  
  Including ruby.h before any fmod header fixed the problem.
  
  No idea why this is the case, but whatever.
  
  
• Link errors : InterlockedBitTestAndComplement, MemoryBarrier, RtlSecureZeroMemory