i can start wings from a term but unfortuantely not from the menu (using waimea as WM). the shell from which i called "startx" shows the following 2 lines: Eshell V.5.2.3.3 (abort with ^G) ** Terminating erlang (nonode@nohost) ** while the first one is normal, the second one leaves _me_ with no information why it doesn't start ... btw: calling the commands of /usr/bin/wings from the waimea-menu doesn't work either - same result as described above. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: nothing - aborted with the following line: ** Terminating erlang (nonode@nohost) ** Expected Results: open the wings3d-application while trying to look for the cause i discovered that the /usr/bin/wings-script uses a variable $WINGS_ROOT which is set to "/usr/lib/erlang/lib/wings" - as this path didn't exist I linked it to "/usr/lib/erlang/lib/wings-0.98.07d". Maybe this should be added in the wings-ebuild.
this should have happened ... notice this line in the ebuild: dosym ${WINGS_PATH} ${ERL_LIBS}/${PN} (where WINGS_PATH is ${ERL_PATH}/${P}) if you remove that symlink by hand and then re-emerge wings, is the symlink created ? do you see any interesting output in the emerge process ?
i just updated wings/esdl ... could you try it out again please ?
oh and i fixed that symlink bug ... that was my bad
I unmerged the old wings- & esdl-versions and emerged the new ones - both went totally fine (just like their predecessors did). the symlink is created. unfortunately still the same errors when starting from the waimea menu - haven't tried it from anyother WM ...
i created this little workaround: instead of calling /usr/bin/wings directly I start a term executing it for me (Eterm -e /usr/bin/wings)
could you check that the wings script has '-detach' in it ? the script should have this as the last line: erl -pa -detach $ESDL_ROOT/ebin $WINGS_ROOT/ebin -run wings_start start_halt if it doesnt, please change the last line of the script to that and try to run it again from waimea
added "-detach" but it didn't change anything - still the same error ...
ok, i found the answer ... use the '-noshell' option ... the reason for the crashing is that by default the erlang shell loads up and accepts input while it runs the requested erlang binaries ... when you launch it from a window manager like that though the program is not given a stdin to read from so in this case it died ... -noshell causes erlang to not launch that aspect of itself fixed in cvs http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/media-gfx/wings/files/wings.sh.diff?r1=1.2&r2=1.3
cool - works perfectly! thx
