Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
faq:nix [2020/03/22 00:49] – [Disk Space] Bloaty bloaty digital man | faq:nix [2020/03/22 14:45] – [SDL errors] mention the xhost solution digital man |
---|
| |
To elaborate, [[util:SBBSecho]] uses ''tempnam'' for a specific purpose, which ''mkstemp'' does not do. Additionally ''mkstemp'' is not available in all the C libraries for all the platforms for which Synchronet is built. The //dangers// of ''tempnam'' do not apply to SBBSecho's use of the function. | To elaborate, [[util:SBBSecho]] uses ''tempnam'' for a specific purpose, which ''mkstemp'' does not do. Additionally ''mkstemp'' is not available in all the C libraries for all the platforms for which Synchronet is built. The //dangers// of ''tempnam'' do not apply to SBBSecho's use of the function. |
| |
| ===== SDL errors ===== |
| **Question:**\\ |
| How do I work around SDL_main errors (e.g. ''No protocol specified'' followed by a ''segmentation fault'') that prevent Synchronet applications (e.g. [[util:SCFG]], [[util:EchoCFG]], [[monitor:umonitor]], etc.) built with SDL 1.2 from running? |
| <code> |
| $ /sbbs/exec/scfg |
| No protocol specified |
| No protocol specified |
| No protocol specified |
| Segmentation fault (core dumped) |
| </code> |
| |
| **Answer:**\\ |
| Double check that you can run X applications (e.g. ''xterm'', ''xeyes'') and if you cannot, you may need to grant X access to other user accounts with a command like: |
| xhost +SI:localuser:<username> |
| executed before switching to another user account (e.g. with ''su'' or ''sudo''). |
| |
| Work-arounds: |
| - Clean re-build all of Synchronet without SDL support (include ''WITHOUT_SDL=1'' on the ''make'' command-lines or in your ''localdefs.mk'' file) |
| - Set the ''SDL_VIDEODRIVER'' environment variable to the value of ''dummy'' (e.g. ''EXPORT SDL_VIDEODRIVER=dummy'') before executing the program |
| |
===== See Also ===== | ===== See Also ===== |