UPDATE: SDL3 - getexecpath()

Here is a diff to SDL3 to add getexecpath() support. Index: Makefile =================================================================== RCS file: /cvs/ports/devel/sdl3/Makefile,v retrieving revision 1.9 diff -u -p -u -p -r1.9 Makefile --- Makefile 8 Sep 2026 12:45:28 -0000 1.9 +++ Makefile 11 Sep 2026 06:31:18 -0000 @@ -3,6 +3,7 @@ COMMENT = cross-platform multimedia lib V = 3.4.16 DISTNAME = SDL3-${V} PKGNAME = ${DISTNAME:L} +REVISION = 0 SHARED_LIBS += SDL3 0.1 # 3.4.0 Index: patches/patch-CMakeLists_txt =================================================================== RCS file: patches/patch-CMakeLists_txt diff -N patches/patch-CMakeLists_txt --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patches/patch-CMakeLists_txt 11 Sep 2026 06:31:18 -0000 @@ -0,0 +1,14 @@ +- fs: Use getexecpath() on OpenBSD for GetExePath(). + b7606be372bff4f434d0e2e06ca8a1edd249cde4 + +Index: CMakeLists.txt +--- CMakeLists.txt.orig ++++ CMakeLists.txt +@@ -1159,6 +1159,7 @@ if(SDL_LIBC) + + if(NOT WINDOWS) + check_symbol_exists(fdatasync "unistd.h" HAVE_FDATASYNC) ++ check_symbol_exists(getexecpath "unistd.h" HAVE_GETEXECPATH) + check_symbol_exists(gethostname "unistd.h" HAVE_GETHOSTNAME) + check_symbol_exists(getpagesize "unistd.h" HAVE_GETPAGESIZE) + check_symbol_exists(getresgid "unistd.h" HAVE_GETRESGID) Index: patches/patch-include_build_config_SDL_build_config_h_cmake =================================================================== RCS file: patches/patch-include_build_config_SDL_build_config_h_cmake diff -N patches/patch-include_build_config_SDL_build_config_h_cmake --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patches/patch-include_build_config_SDL_build_config_h_cmake 11 Sep 2026 06:31:18 -0000 @@ -0,0 +1,14 @@ +- fs: Follow up to the initial getexecpath() support + c545b20bd7fbd536a37c00271e6d474acc861a34 + +Index: include/build_config/SDL_build_config.h.cmake +--- include/build_config/SDL_build_config.h.cmake.orig ++++ include/build_config/SDL_build_config.h.cmake +@@ -73,6 +73,7 @@ + #cmakedefine HAVE_DLOPEN 1 + #cmakedefine HAVE_MALLOC 1 + #cmakedefine HAVE_FDATASYNC 1 ++#cmakedefine HAVE_GETEXECPATH 1 + #cmakedefine HAVE_GETENV 1 + #cmakedefine HAVE_GETHOSTNAME 1 + #cmakedefine HAVE_SETENV 1 Index: patches/patch-src_filesystem_unix_SDL_sysfilesystem_c =================================================================== RCS file: patches/patch-src_filesystem_unix_SDL_sysfilesystem_c diff -N patches/patch-src_filesystem_unix_SDL_sysfilesystem_c --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patches/patch-src_filesystem_unix_SDL_sysfilesystem_c 11 Sep 2026 06:31:18 -0000 @@ -0,0 +1,41 @@ +- fs: Use getexecpath() on OpenBSD for GetExePath(). + b7606be372bff4f434d0e2e06ca8a1edd249cde4 +- fs: Follow up to the initial getexecpath() support + c545b20bd7fbd536a37c00271e6d474acc861a34 + +Index: src/filesystem/unix/SDL_sysfilesystem.c +--- src/filesystem/unix/SDL_sysfilesystem.c.orig ++++ src/filesystem/unix/SDL_sysfilesystem.c +@@ -71,7 +71,7 @@ static char *readSymLink(const char *path) + return NULL; + } + +-#ifdef SDL_PLATFORM_OPENBSD ++#if defined(SDL_PLATFORM_OPENBSD) && !defined(HAVE_GETEXECPATH) + static char *search_path_for_binary(const char *bin) + { + const char *envr_real = SDL_getenv("PATH"); +@@ -138,6 +138,15 @@ static char *GetExePath(void) + } +

Re: prusaslicer-2.9.4p2 segfault

With the config I shared, I have reproduced it now on 4 installations.

The 4'th installation is a fresh OpenBSD 8.0 beta on one machine. I put my prusa config there and have the very same crash on prusaslicer-2.9.6
with just different address:
[error]   UserAccount: Failed to read token - no datafile found.
Actually to filter out the debug-prusaslicer thing I installed it also on the 8.0 beta: made no difference at all. Well I did not have any high hopes for it as it seems to be the very same but with debug symbols compiled in.

@Renato : I cant figure out what you are not able to reproduce: how can I help ?
do you need a full package listing ? or just maybe the output of pkg_info -mq ?
Just don't ask me to start compiling stuff with ports or what not ... that's not a rabbit hole I'm ready to go down into yet on OpenBSD.

Il giorno gio 10 set 2026 alle ore 07:57 Renato Aguiar <renato@renatoaguiar.net> ha scritto:

On Thu, Sep 10 2026, louigi 600 wrote:

>
> I do however wonder what was the reason for releasing prusaslicer-2.9.4p2
> when the previous version was working ?

Obviously, I couldn't reproduce that crash on prusaslicer-2.9.4p2. I've
seen it in previous versions though, but it was rare, only happened
during startup, and it would work fine after running it again.

>
> I do see a snapshot version
> https://ftp.hostserver.de/pub/OpenBSD/snapshots/packages/amd64/prusaslicer-2.9.6.tgz
> I wonder if that can be used on 7.9 ?

I don't think so. You'd have to install the snapshot to use that
package.

If you want to make sure that next release has no regressions, you could
help testing prusaslicer 2.9.6 in the snapshot and report any bugs
before the ports tree is frozen.