Author Topic: [SOLVED] Unable to get fs2_open.log on Linux  (Read 1246 times)

0 Members and 1 Guest are viewing this topic.

[SOLVED] Unable to get fs2_open.log on Linux
Hi,

I am trying to make The Babylon Project works on my Linux Box (Gentoo Linux). Unfortunatelly, the game crash on starting. I have compiled the 3.6.10 sources with autogen.sh flag "--enable-debug" but when following the procedure described in another thread to get the fs2_open.log, I do not found the logfile in data/.

The access rights for the directory are:

drwxrwx--- 7 root games       4096 Nov 12 16:47 data

During the compilation of the source code I have seen the following compilation flag "-DNDEBUG=1" which seems to suggest  that the debugging is activated.

Does someone have any hint at why the log file is not created?
« Last Edit: November 27, 2010, 08:55:44 am by montaropdf »
Luke, use the F.O.S.S.!!!

 

Offline The E

  • He's Ebeneezer Goode
  • Global Moderator
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: Unable to get fs2_open.log on Linux
On Linux, the log is saved in ~/.fs2_open/data.

Also, please don't use the .10 source. Pleeeeeeaaaaasssseeeeee get a fresh svn checkout. Basically, we can't help you with any problem or bug you encounter with builds that old.
Let there be light
Let there be moon
Let there be stars and let there be you
Let there be monsters and let there be pain
Let us begin to feel again
--Devin Townsend, Genesis

 
Re: Unable to get fs2_open.log on Linux
Ok, I'll try with the 3.6.12.

I looked in .fs2_open/data, but no logfile.

To allow multiple TC running concurrently on gentoo linux, the ebuild (gentoo script to install an application), I am currently working on with some other people, modify the variable Osreg_user_dir to contain the location of the TC. In my case, /opt/babylon. This was suggested by some people like Iss Mneur and chief1983 on this entry:

http://bugs.gentoo.org/show_bug.cgi?id=107081

I will keep you inform after I have tried with the newer version of FSO SCP.


Luke, use the F.O.S.S.!!!

 

Offline Iss Mneur

  • 210
  • TODO:
Re: Unable to get fs2_open.log on Linux
Okay. To be clear, when we say ".fs2_open", we are referring the directory that is specified by Osreg_user_dir in the source that you are using.  By default that is ".fs2_open", if you changed the source, then it will be in whatever directory that Osreg_user_dir points to.
"I love deadlines. I like the whooshing sound they make as they fly by." -Douglas Adams
wxLauncher 0.9.4 public beta (now with no config file editing for FRED) | wxLauncher 2.0 Request for Comments

 
Re: Unable to get fs2_open.log on Linux
Hi,

With version 3.6.12 downloaded from http://swc.fs2downloads.com/builds, I got the following error during compilation:
 
Code: [Select]
ar cru libcode.a ai.o aibig.o aicode.o aigoals.o aiturret.o ai_profiles.o animplay.o packunpack.o asteroid.o autopilot.o bmpman.o camera.o cfile.o cfilearchive.o cfilelist.o cfilesystem.o cmdline.o cmeasure.o controlsconfig.o controlsconfigcommon.o cutscenes.o decoder16.o decoder8.o movie.o mve_audio.o mvelib.o mveplayer.o oggplayer.o ddsutils.o debris.o console.o timerbar.o decals.o demo.o exceptionhandler.o trackirglobal.o fireballs.o warpineffect.o fs2netd_client.o tcp_client.o tcp_socket.o contexthelp.o gameplayhelp.o gamesequence.o alphacolors.o crypt.o def_files.o safe_strings.o safe_strings_test.o systemvars.o version.o 2d.o font.o generic.o grbatch.o gropengl.o gropenglbmpman.o gropengldraw.o gropenglextension.o gropengllight.o gropenglpostprocessing.o gropenglshader.o gropenglstate.o gropengltexture.o gropengltnl.o grstub.o hud.o hudartillery.o hudbrackets.o hudconfig.o hudescort.o hudets.o hudlock.o hudmessage.o hudnavigation.o hudobserver.o hudparse.o hudreticle.o hudshield.o hudsquadmsg.o hudtarget.o hudtargetbox.o hudwingmanstatus.o iff_defs.o cftp.o chttpget.o inetgetfile.o key.o keycontrol.o mouse.o timer.o jpgutils.o jumpnode.o lab.o wmcgui.o lighting.o fhash.o localize.o fix.o floating.o fvi.o spline.o staticrand.o vecmat.o barracks.o credits.o fishtank.o mainhallmenu.o mainhalltemp.o optionsmenu.o optionsmenumulti.o playermenu.o readyroom.o snazzyui.o techmenu.o trainingmenu.o missionbriefcommon.o missioncampaign.o missiongoals.o missiongrid.o missionhotkey.o missionload.o missionlog.o missionmessage.o missionparse.o missiontraining.o chatbox.o fictionviewer.o missionbrief.o missioncmdbrief.o missiondebrief.o missionloopbrief.o missionpause.o missionrecommend.o missionscreencommon.o missionshipchoice.o missionstats.o missionweaponchoice.o redalert.o modelanim.o modelcollide.o modelinterp.o modeloctant.o modelread.o neb.o neblightning.o chat_api.o multi.o multilag.o multimsgs.o multiteamselect.o multiui.o multiutil.o multi_campaign.o multi_data.o multi_dogfight.o multi_endgame.o multi_ingame.o multi_kick.o multi_log.o multi_obj.o multi_observer.o multi_options.o multi_pause.o multi_pinfo.o multi_ping.o multi_pmsg.o multi_pxo.o multi_rate.o multi_respawn.o multi_sexp.o multi_team.o multi_voice.o multi_xfer.o psnet.o psnet2.o stand_gui.o stand_gui-unix.o collidedebrisship.o collidedebrisweapon.o collideshipship.o collideshipweapon.o collideweaponweapon.o deadobjectdock.o objcollide.o objectdock.o object.o objectshield.o objectsort.o parseobjectdock.o waypoint.o observer.o palman.o encrypt.o lua.o parselo.o scripting.o sexp.o particle.o pcxutils.o pngutils.o physics.o managepilot.o playercontrol.o popup.o popupdead.o radar.o radarorb.o radarsetup.o 3dclipper.o 3ddraw.o 3dlaser.o 3dmath.o 3dsetup.o afterburner.o awacs.o shield.o ship.o shipcontrails.o shipfx.o shiphit.o species_defs.o nebula.o starfield.o supernova.o medals.o scoring.o stats.o tgautils.o button.o checkbox.o gadget.o icon.o inputbox.o keytrap.o listbox.o radio.o scroll.o slider.o slider2.o uidraw.o uimouse.o window.o beam.o corkscrew.o emp.o flak.o muzzleflash.o shockwave.o swarm.o trails.o weapons.o joy-unix.o eventmusic.o gamesnd.o objectsnd.o ogg.o audiostr-openal.o audiostr.o acm-openal.o ds.o ds3d.o dscap.o rbaudio.o rtvoice.o sound.o codec1.o fsspeech.o speech.o voicerec.o  osapi_unix.o osregistry_unix.o outwnd_unix.o stubs.o
x86_64-pc-linux-gnu-ranlib libcode.a
x86_64-pc-linux-gnu-g++ -m64 -march=athlon64 -ansi -pedantic -DLUA_USE_LINUX -O0 -g -Wall -Wextra -Wno-unused-parameter -Wno-write-strings -Wshadow -funroll-loops -DLUA_USE_APICHECK -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT     -fsigned-char -Wno-unknown-pragmas  -Wno-deprecated -Wno-char-subscripts -I../lua -march=athlon64 -O2 -pipe -g  -lSDL -lpthread -L/usr/lib64 -lvorbis -lm -lvorbisfile -L/usr/lib64 -ltheora -L/usr/lib64 -logg -lpng -lGL -lGLU -lopenal -Wl,-O1 -Wl,--as-needed -o fs2_open_INF_d freespace.o levelpaging.o libcode.a ../libjpeg/libjpeg.a ../lua/liblua.a
libcode.a(modelinterp.o): In function `generate_vertex_buffers(bsp_info*, polymodel*)':
/var/tmp/portage/games-action/tbp-3.6.12/work/fs2_open_3_6_12_src/code/model/modelinterp.cpp:5166: undefined reference to `same_vert(vertex*, vertex*, vec3d*, vec3d*)'
/var/tmp/portage/games-action/tbp-3.6.12/work/fs2_open_3_6_12_src/code/model/modelinterp.cpp:5171: undefined reference to `same_vert(vertex*, vertex*, vec3d*, vec3d*)'
collect2: ld returned 1 exit status
make[1]: *** [fs2_open_INF_d] Error 1

in addition to debug I have also activated the flag inferno and speech.

I see in the compilation commands '-D_DEBUG=1', is it the correct name to activate debugging?

Luke, use the F.O.S.S.!!!

 

Offline Iss Mneur

  • 210
  • TODO:
Re: Unable to get fs2_open.log on Linux
Hi,

With version 3.6.12 downloaded from http://swc.fs2downloads.com/builds, I got the following error during compilation:
 [snip]
in addition to debug I have also activated the flag inferno and speech.

I see in the compilation commands '-D_DEBUG=1', is it the correct name to activate debugging?


I don't know what to tell you.  The code builds fine on my Ubuntu system.  I will have to setup a Gentoo system so that I can test in the same environment, so I will check back later on this.

In the mean time, does 3.6.12 build when you do it manual (ie. not in portage)?
Could you attach the entire output of the build as well (including the run of autogen.sh and configure).

It seems that _DEBUG would be the correct define, though I thought that we also used DEBUG (at least on windows).
"I love deadlines. I like the whooshing sound they make as they fly by." -Douglas Adams
wxLauncher 0.9.4 public beta (now with no config file editing for FRED) | wxLauncher 2.0 Request for Comments

 
Re: Unable to get fs2_open.log on Linux
Hi,

attached is a zip archive with the log of compilation with and without portage + the ebuild I am working on, just in case you see directly from it whats wrong.

As you will see, the compilation run without problem when done out of portage.

For completeness, I am building the source on and AMD 64bit CPU.

[attachment deleted by admin]
Luke, use the F.O.S.S.!!!

 

Offline Iss Mneur

  • 210
  • TODO:
Re: Unable to get fs2_open.log on Linux
Well, I think I have solved it.

The cause of the issue is two fold. There is a code bug, same_vert was decorated inline at its definition. But same_vert is declared in the header and because the inline definition of the function is not in the header, when the compiler actually decided to follow the directive, the function same_vert is not available outside of its declared compilation unit (2d.cpp).

The reason that this was never noticed is that our building recommendations are actually that you not use -O because it causes various runtime issues.

So the there are two solutions to the problem:
1) I have attached a patch which moves the offending function to where it should be so that inlining will work correctly.
2) Don't compile FSO with any -O option set (which will mean that you have to modify the ebuild to filter out -O from your portage settings).

Personally I would just suggest going with number 2. But there have been previous anecdotes of -O2 and -O3 actually working and not causing the engine to screwup, so if you do decide to go with option 1, we would be interested in your experience.  But keep in mind, if we find that you are having inexplicable problems removing -O options will be the first thing that we ask you to do.

Also for the record, using that ebuild, your log will be in $HOME/.tbp_fso/data.

Hopefully, this will allow us to get on with figuring out why you are having strange errors (though the -O setting could be part of the problem for 3.6.10 from the start).



Also, I noticed that our autogen.sh supposedly supports not running configure, but I haven't been able to figure out how to invoke is so, I have also attached a patch that fixes that as well.  To make autogen.sh not run configure, invoke it with --noconfigure as the first parameter.

Edit: I was being a dummy.  Call autogen.sh as NOCONFIGURE=1 ./autogen.sh to not run configure.

[attachment deleted by admin]
« Last Edit: November 15, 2010, 03:14:34 pm by Iss Mneur »
"I love deadlines. I like the whooshing sound they make as they fly by." -Douglas Adams
wxLauncher 0.9.4 public beta (now with no config file editing for FRED) | wxLauncher 2.0 Request for Comments

 

Offline chief1983

  • Still lacks a custom title
  • 212
  • ⬇️⬆️⬅️⬅️🅰➡️⬇️
    • Minecraft
    • Skype
    • Steam
    • Twitter
    • Fate of the Galaxy
Re: Unable to get fs2_open.log on Linux
I have uploaded a new source tarball for 3.6.12 that fixes the inline issue.  http://swc.fs2downloads.com/builds/fs2_open_3_6_12.tgz

I got rid of the _src this time to match the 3.6.10 source filename.
« Last Edit: November 15, 2010, 04:48:25 pm by chief1983 »
Fate of the Galaxy - Now Hiring!  Apply within | Diaspora | SCP Home | Collada Importer for PCS2
Karajorma's 'How to report bugs' | Mantis
#freespace | #scp-swc | #diaspora | #SCP | #hard-light on EsperNet

"You may not sell or otherwise commercially exploit the source or things you created based on the source." -- Excerpt from FSO license, for reference

Nuclear1:  Jesus Christ zack you're a little too hamyurger for HLP right now...
iamzack:  i dont have hamynerge i just want ptatoc hips D:
redsniper:  Platonic hips?!
iamzack:  lays

 
Re: Unable to get fs2_open.log on Linux
Hi,


With the last FSO 3.6.12 uploaded by chief1983 and the right data files (mediavps, ...), TBP is working just fine and I can have the logfile created in debug mode.


Thanks for the help,


Case closed.
Luke, use the F.O.S.S.!!!