Jump to content


Photo

Warnings in Compiler Output

log4.txt Warning

  • Please log in to reply
1 reply to this topic

#1 Jean

Jean

    Newbie

  • Members
  • Pip
  • 1 posts
  • LocationMontreal, Canada

Posted 10 September 2015 - 03:43 PM

When I look at the Compiler Output either from my models or my colleagues' model I can see a bunch of warnings in the log4.txt part.  Is that normal?  I have copied below an example.

 

Thanks,

 

Jean

 

"-------------
log4.txt:
Could Not Find C:\DOCUME~1\offmae01\LOCALS~1\Temp\Phoenix\DME_BF~1\Work\*.o
Warning: resolving _GETPRED by linking to _GETPRED@36
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
Warning: resolving _SETETA by linking to _SETETA@4
Warning: resolving _SETISUB by linking to _SETISUB@4
Warning: resolving _PACKPARAMETERS1 by linking to _PACKPARAMETERS1@24
Warning: resolving _SETMAINSTDEV by linking to _SETMAINSTDEV@4
Warning: resolving _SETTHETA by linking to _SETTHETA@4
Warning: resolving _THROWMODELEXCEPTION by linking to _THROWMODELEXCEPTION@0
Warning: resolving _GETNERROR by linking to _GETNERROR@0
Warning: resolving _GETODELEVELUSED by linking to _GETODELEVELUSED@4
Warning: resolving _GETNSIGMA by linking to _GETNSIGMA@0
Warning: resolving _ALLOWGAUSSIANFIT by linking to _ALLOWGAUSSIANFIT@0
Warning: resolving _GETNTHETA by linking to _GETNTHETA@0
Warning: resolving _UNPACKPARAMETERS1 by linking to _UNPACKPARAMETERS1@24
Warning: resolving _GETSAEMTHETAINFO by linking to _GETSAEMTHETAINFO@8
Warning: resolving _GETSAEMCMATRIX by linking to _GETSAEMCMATRIX@8
Warning: resolving _GETSAEMCMATRIXSIZE by linking to _GETSAEMCMATRIXSIZE@12
Warning: resolving _CANUSESAEM by linking to _CANUSESAEM@0
Warning: resolving _REPORTPROGRESS by linking to _REPORTPROGRESS@4
Warning: resolving _STARTPROGRESS by linking to _STARTPROGRESS@0
Warning: resolving _FCNETA by linking to _FCNETA@12
Warning: resolving _TYPXPARAMETERS1 by linking to _TYPXPARAMETERS1@24
Warning: resolving _FCNDFDETA by linking to _FCNDFDETA@16
Warning: resolving _NEWGETPRED by linking to _NEWGETPRED@44
Warning: resolving _GETTHETALIMITS by linking to _GETTHETALIMITS@8
Warning: resolving _GETNOBS1 by linking to _GETNOBS1@8
Warning: resolving _GETSCRAMBLE by linking to _GETSCRAMBLE@0
Warning: resolving _GETPEMRUNALL by linking to _GETPEMRUNALL@0
Warning: resolving _GETBURNIN by linking to _GETBURNIN@0
Warning: resolving _GETSIRSAMP by linking to _GETSIRSAMP@0
Warning: resolving _GETRUNFROMUI by linking to _GETRUNFROMUI@0
Warning: resolving _GETACCRATIO by linking to _GETACCRATIO@0
Warning: resolving _GETMCPEM by linking to _GETMCPEM@0
Warning: resolving _GETMAPASSIST by linking to _GETMAPASSIST@0
Warning: resolving _GETISAMPLE by linking to _GETISAMPLE@0
Warning: resolving _GETIMPSAMPDOF by linking to _GETIMPSAMPDOF@0
Warning: resolving _FCNTHETA1 by linking to _FCNTHETA1@12
Warning: resolving _TRUNCOMEGA by linking to _TRUNCOMEGA@4
Warning: resolving _GETRETURNCODE@4 by linking to _GETRETURNCODE
Warning: resolving _GETEPS_SHRINK@4 by linking to _GETEPS_SHRINK
Warning: resolving _GETLAPLACEENGINE@4 by linking to _GETLAPLACEENGINE
Warning: resolving _GETOMEGACHOL@8 by linking to _GETOMEGACHOL
Warning: resolving _ENGINE7FONM@60 by linking to _ENGINE7FONM
Warning: resolving _ENGINE7LAGLNP@64 by linking to _ENGINE7LAGLNP
Warning: resolving _ENGINE7LAGL@64 by linking to _ENGINE7LAGL
Warning: resolving _ENGINE7FO@60 by linking to _ENGINE7FO
Warning: resolving _ENGINE7FOCE@60 by linking to _ENGINE7FOCE
Warning: resolving _ENGINE7EM@64 by linking to _ENGINE7EM
Warning: resolving _ENGINE7TWOSTAGE@64 by linking to _ENGINE7TWOSTAGE
Warning: resolving _GETWORKINGSTORAGESIZES@36 by linking to _GETWORKINGSTORAGESIZES
Warning: resolving _GETOMEGA@16 by linking to _GETOMEGA
Warning: resolving _GETTHETA@8 by linking to _GETTHETA
Warning: resolving _DLSODE@68 by linking to _DLSODE
Warning: resolving _DLSODA@68 by linking to _DLSODA
Warning: resolving _DVERK@40 by linking to _DVERK
Warning: resolving _DGPADM@44 by linking to _DGPADM
Warning: resolving _GETLAPLACE@4 by linking to _GETLAPLACE
Warning: resolving _SETPCWRESNREP@4 by linking to _SETPCWRESNREP
Warning: resolving _SETTOLMODLINZ@4 by linking to _SETTOLMODLINZ
Warning: resolving _SETNDIGITBLUP@4 by linking to _SETNDIGITBLUP
Warning: resolving _SETMETHODBLUP@4 by linking to _SETMETHODBLUP
Warning: resolving _SETTOLSTDERR@4 by linking to _SETTOLSTDERR
Warning: resolving _SETNDIGITLAGL@4 by linking to _SETNDIGITLAGL
Warning: resolving _SETMETHODLAGL@4 by linking to _SETMETHODLAGL
Warning: resolving _SETSTDERR@4 by linking to _SETSTDERR
Warning: resolving _SETVERBOSE@4 by linking to _SETVERBOSE
Warning: resolving _SETFOCEHESS@4 by linking to _SETFOCEHESS
Warning: resolving _SETNORDERAGQ@4 by linking to _SETNORDERAGQ
Warning: resolving _SETRESTART@4 by linking to _SETRESTART
Warning: resolving _SETNP@4 by linking to _SETNP
Warning: resolving _SETANAGRAD@4 by linking to _SETANAGRAD
Warning: resolving _DRAN3SET@4 by linking to _DRAN3SET
Warning: resolving _DRAN3GET@4 by linking to _DRAN3GET
Warning: resolving _DRAN3@4 by linking to _DRAN3
Warning: resolving _GETCDFYOBS@8 by linking to _GETCDFYOBS
Warning: resolving _GETCDFPCWRES@8 by linking to _GETCDFPCWRES
Warning: resolving _GETPCWRES@8 by linking to _GETPCWRES
Warning: resolving _GETCWRES@8 by linking to _GETCWRES
Warning: resolving _GETWRES@8 by linking to _GETWRES
Warning: resolving _GETWIRES@8 by linking to _GETWIRES
Warning: resolving _GETNOBS@8 by linking to _GETNOBS
Warning: resolving _GETOMEGACHOLVAR@8 by linking to _GETOMEGACHOLVAR
Warning: resolving _GETEIGENVALUES@24 by linking to _GETEIGENVALUES
Warning: resolving _GETVINF@4 by linking to _GETVINF
Warning: resolving _GETNVINF@4 by linking to _GETNVINF
"



#2 Ana Henry

Ana Henry

    Advanced Member

  • Val_Members
  • PipPipPip
  • 232 posts

Posted 10 September 2015 - 10:00 PM

Hello,

These warnings in log4.txt file are normal and they do not indicate any problem with your fit.  In the next versions you will not see them any longer. 

 

Ana Henry

Phoenix Project Manager


  • Jean likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users