Page 1 of 1
r734 compile possible problems
Posted: Fri Jan 29, 2010 20:36
by Enjay
Just did a clean and rebuild and got the following:
I'm sure that I remember this first one as having been there for ages and being harmless but I can't find it with a forum search so, here it is just in case:
Code: Select all
9>.\trustinfo.txt:manifest authoring warning 81010002:Unrecognized Element "trustInfo" in namespace "urn:schemas-microsoft-com:asm.v3".
[edit] I just realised that this next one has
already been reported and the fix is for me to edit the header file in question. So, I'll give that a go and I've spoilered it to hide it.
[spoiler]This second one looks as if it is related to SDK stuff so it's probably not GZdoom
Code: Select all
16>C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\intrin.h(944) : error C2733: second C linkage of overloaded function '_interlockedbittestandset' not allowed
16> C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\intrin.h(944) : see declaration of '_interlockedbittestandset'
16>C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\intrin.h(945) : error C2733: second C linkage of overloaded function '_interlockedbittestandreset' not allowed
16> C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\intrin.h(945) : see declaration of '_interlockedbittestandreset'
16>Generating Code...
[/spoiler][/edit]
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 20:49
by Enjay
OK, I've done the commenting out and added the define as listed in the linked thread. I'm now getting:
Code: Select all
4>Linking...
4>gl_nodes.obj : error LNK2019: unresolved external symbol "void __fastcall P_LoadZNodes(class FileReader &,unsigned int)" (?P_LoadZNodes@@YIXAAVFileReader@@I@Z) referenced in function "bool __fastcall CheckCachedNodes(struct MapData *)" (?CheckCachedNodes@@YI_NPAUMapData@@@Z)
4>../gzdoom.exe : fatal error LNK1120: 1 unresolved externals
Which looks to me like it might be GZdoom rather than SDK related.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 21:40
by Graf Zahl
How did you break that? Best do a complete rebuild. That part works fine for me.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 21:45
by Enjay
Cleaned, rebuilt and...
Code: Select all
16>Linking...
16>gl_nodes.obj : error LNK2019: unresolved external symbol "void __fastcall P_LoadZNodes(class FileReader &,unsigned int)" (?P_LoadZNodes@@YIXAAVFileReader@@I@Z) referenced in function "bool __fastcall CheckCachedNodes(struct MapData *)" (?CheckCachedNodes@@YI_NPAUMapData@@@Z)
16>../gzdoom.exe : fatal error LNK1120: 1 unresolved externals
I'll try a completely new check out and see what happens.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 21:55
by Enjay
Hmmm...
Code: Select all
16>Linking...
16>LINK : program database c:\Doom\GZdoomSource\gzdoomcomp\Debug\zdoomd.pdb missing; performing full link
16>gl_nodes.obj : error LNK2019: unresolved external symbol "void __cdecl P_LoadZNodes(class FileReader &,unsigned int)" (?P_LoadZNodes@@YAXAAVFileReader@@I@Z) referenced in function "bool __cdecl CheckCachedNodes(struct MapData *)" (?CheckCachedNodes@@YA_NPAUMapData@@@Z)
16>../gzdoomd.exe : fatal error LNK1120: 1 unresolved externals
Of course, that does imply to me that it's something to do with my system. All I did was:
Comment out the 2 lines listed in intrin.h:
_MACHINEI(unsigned char _interlockedbittestandset(long *a, long b))
__MACHINEI(unsigned char _interlockedbittestandreset(long *a, long b))
Manually add this define to the include file 'xinput.h'
#define XUSER_MAX_COUNT 4
Would either of those lead to a problem in this area?
[edit] Not surprisingly, seeing as how the error involves a GL file, I was able to compile a cleaned Zdoom. I'm off to check if my OpenGL header files are up to date. [/edit]
[edit2] Nope, that's not the problem. [/edit2]
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 22:20
by Enjay
and after updating my own modified copy of the code to 734 and trying to compile it, it too fails in the same way.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 22:26
by Enjay
Four posts in a row.
If I revert to r732 I can compile. If I then update to r733, I get the linking error.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 22:35
by Gez
I get the same unresolved external.
To be honest, there are some changes in r733 that I do not understand. Compare:
http://mancubus.net/svn/gzdoom/trunk/sr ... athrev=733
http://zdoom.org/svndiff/2138/zdoom/tru ... etup.cpp#0
I think the ZDoom p_setup overwrote completely the GZDoom one, so important GL stuff disappeared. I reverted p_setup to r732, then put manually the ZDoom change, and it compiled without problems.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 23:05
by Enjay
At least I can stop looking for things that I may have got wrong somewhere.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 23:08
by Graf Zahl
Indeed. I accidentally overwrote it after testing stuff and that got committed afterward.
Re: r734 compile possible problems
Posted: Fri Jan 29, 2010 23:32
by Enjay
Yup, 735 fixes it for me. Thanks.
Re: r734 compile possible problems
Posted: Sat Jan 30, 2010 2:13
by jbailey8
Compiles cleanly, no problems here....