Weird rm -f in compilation log

  • Hi
    ist this rm -f command necessary. I wonder because after that I get tons of compile errors. Where
    can I disable this?
    Many thanks
    g++ -c -m32 -pipe -O2 -Wall -W -fPIC -DXPLM200 -DAPL=0 -DIBM=0 -DLIN=1 -I/usr/share/qt4/mkspecs/linux-g++-32 -I../plugin_source -I../plugin_source -I../plugin_source/gizmo_lua_api -I../../SDK/CHeaders/XPLM -I../../SDK/CHeaders/Wrappers -I../../SDK/CHeaders/Widgets -I/usr/local/include/bullet -I. -o api_third_party_docs.o ../plugin_source/gizmo_lua_api/api_third_party_docs.cpp
    ../plugin_source/gizmo_lua_api/api_third_party_docs.cpp:74: warning: ignoring #pragma mark io
    ../plugin_source/gizmo_lua_api/api_third_party_docs.cpp:100: warning: ignoring #pragma mark math
    rm -f
    g++ -m32 -Wl,-O1 -shared -o AES.o b64.o BulletPhysicsHooks.o gizmo_httpd.o GLee.o luagl.o luagl_util.o luaglu.o md5.o NASA_TurboJetSim_Solver.o StringTools.o TerrainMap.o tgaTools.o XDataRefCustom.o XMiscUtils.o XParticleEngine.o XPlaneHooks.o XTrig.o api_airframe.o api_event_docs.o api_third_party_docs.o -llua -lBulletDynamics -lBulletCollision -lLinearMath -lcurl -lopenal -lalut
    AES.o: In function AES::PayloadSizeForFile(char const*)': AES.cpp:(.text+0x9b55): undefined reference tofopen'
    AES.cpp:(.text+0x9b84): undefined reference to fclose' b64.o: In functionb64(int, char*, char*, int)':
    b64.cpp:(.text+0x76d): undefined reference to fopen' b64.cpp:(.text+0x797): undefined reference tofopen'
    b64.cpp:(.text+0x7e0): undefined reference to fclose' b64.cpp:(.text+0x7fa): undefined reference tofclose'

  • make removes the file because it is built in the next step (g++ -m32 -Wl,-O1 -shared -o ...). There errors you receive are not caused by this rm statement. You are most probably missing a library and/or you are mixing different library versions.

  • Would you be able to sort missing or wrong headers if i post the complete log?
    I'm stuck...or better can I send you a pm?

  • Well, is it possible that you mix C and C++ code here and you do not use extern "C" when facing C code?

  • How should I find out which headers need: extern "C"?

Log in to reply

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.