Trying to compile War3ft for AMXMODX VERSION 1.55

Read log files for errors! If this fails, come here for help

Moderator: Forum Moderator

Locked
User avatar
ghostbuster
Peon
Posts: 6
Joined: Wed Aug 31, 2005 6:53 am
Location: Sweden
Contact:

Trying to compile War3ft for AMXMODX VERSION 1.55

Post by ghostbuster » Mon Sep 05, 2005 4:38 am

Hi there !
Trying to compile War3ft for AMXMODX VERSION 1.55 with the following result. It's all clean download no changes made.

//// warcraft3FT.sma
// war3ft/XP.inl(179 -- 180) : warning 213: tag mismatch
// war3ft/XP.inl(180 -- 181) : warning 213: tag mismatch
// war3ft/XP.inl(181 -- 182) : warning 213: tag mismatch
// war3ft/XP.inl(182 -- 184) : warning 213: tag mismatch
// war3ft/XP.inl(184 -- 185) : warning 213: tag mismatch
// war3ft/XP.inl(185 -- 186) : warning 213: tag mismatch
// war3ft/XP.inl(186 -- 187) : warning 213: tag mismatch
// war3ft/XP.inl(187 -- 189) : warning 213: tag mismatch
// war3ft/XP.inl(189 -- 190) : warning 213: tag mismatch
// war3ft/XP.inl(190 -- 191) : warning 213: tag mismatch
// war3ft/XP.inl(191 -- 192) : warning 213: tag mismatch
// war3ft/XP.inl(192 -- 193) : warning 213: tag mismatch
// war3ft/XP.inl(193 -- 194) : warning 213: tag mismatch
// war3ft/XP.inl(194 -- 195) : warning 213: tag mismatch
// war3ft/XP.inl(195 -- 196) : warning 213: tag mismatch
// war3ft/XP.inl(196 -- 197) : warning 213: tag mismatch
// war3ft/XP.inl(197 -- 198) : warning 213: tag mismatch
// war3ft/XP.inl(198 -- 199) : warning 213: tag mismatch
// war3ft/XP.inl(199 -- 200) : warning 213: tag mismatch
// war3ft/XP.inl(200 -- 201) : warning 213: tag mismatch
// war3ft/XP.inl(201 -- 202) : warning 213: tag mismatch
// war3ft/XP.inl(202 -- 203) : warning 213: tag mismatch
// war3ft/XP.inl(203 -- 204) : warning 213: tag mismatch
// war3ft/XP.inl(204 -- 205) : warning 213: tag mismatch
// war3ft/XP.inl(205 -- 206) : warning 213: tag mismatch
// war3ft/XP.inl(206 -- 207) : warning 213: tag mismatch
// war3ft/XP.inl(207 -- 208) : warning 213: tag mismatch
// war3ft/XP.inl(208 -- 209) : warning 213: tag mismatch
// war3ft/XP.inl(209 -- 210) : warning 213: tag mismatch
// war3ft/XP.inl(210 -- 211) : warning 213: tag mismatch
// war3ft/XP.inl(211 -- 212) : warning 213: tag mismatch
// war3ft/XP.inl(212 -- 213) : warning 213: tag mismatch
// war3ft/XP.inl(213 -- 214) : warning 213: tag mismatch
// war3ft/XP.inl(214 -- 215) : warning 213: tag mismatch
// war3ft/XP.inl(215 -- 216) : warning 213: tag mismatch
// war3ft/XP.inl(216 -- 217) : warning 213: tag mismatch
// war3ft/XP.inl(217 -- 218) : warning 213: tag mismatch
// war3ft/XP.inl(218 -- 219) : warning 213: tag mismatch
// war3ft/XP.inl(219 -- 220) : warning 213: tag mismatch
// war3ft/XP.inl(220 -- 221) : warning 213: tag mismatch
// war3ft/XP.inl(221 -- 223) : warning 213: tag mismatch
// Header size: 6208 bytes
// Code size: 309816 bytes
// Data size: 131288 bytes
// Stack/heap size: 16384 bytes; max. usage is unknown, due to recursion
// Total requirements: 463696 bytes

User avatar
Lazarus Long
Lead PITA SOB
Posts: 618
Joined: Tue Jul 05, 2005 9:24 pm

Post by Lazarus Long » Mon Sep 05, 2005 6:15 am

Hello, ghostbuster:

These wrnings are normal when you compile for DoD.

Regards,
Lazarus

User avatar
ghostbuster
Peon
Posts: 6
Joined: Wed Aug 31, 2005 6:53 am
Location: Sweden
Contact:

Post by ghostbuster » Mon Sep 05, 2005 6:19 am

It is not a DoD server its a CZserver :) and does war3 works normally dispite of the warnings.
The warning did not apply when I tried 1.50.
Image

User avatar
Lazarus Long
Lead PITA SOB
Posts: 618
Joined: Tue Jul 05, 2005 9:24 pm

Post by Lazarus Long » Mon Sep 05, 2005 6:50 am

ghostbuster:

I'm absolutely sure you are compiling for DoD, if you were compiling for CS you would never see those warnings.

They are harmless, the plugin will run without a problem (well, in your case it won't if you try to run that plugin in CS...).

Regards,
Lazarus

User avatar
ghostbuster
Peon
Posts: 6
Joined: Wed Aug 31, 2005 6:53 am
Location: Sweden
Contact:

Post by ghostbuster » Mon Sep 05, 2005 6:55 am

Tnx 4 your answer ! I will have to take a closer look @ my configs then.

:oops: :oops: :oops:
Image

User avatar
Geesu
<b>King of the world!</b>
Posts: 3159
Joined: Tue Jul 05, 2005 9:24 pm
Contact:

Post by Geesu » Mon Sep 05, 2005 11:52 am

change #define MOD 1 to #define MOD 0 at the top of warcraft3ft.sma
No Support via PM

Locked