| |
| |
On 1/29/23 09:06, Zsolt Pajor-Gyulai wrote:
The problem was that a recent commit made fluid call
Fl::add_fd() in a static initializer thread.
For some reason, Fl::add_fd() opens the display,
specifically on macOS, not on other platforms.
Matt removed this early call to add_fd().
I find the problem of hanging build process to be
fixed now.
Hopefully that also solves the OP's problem.
I might be too uninitiated, but what is the
suggested solution? To use the dev version 1.4.0?
I'm coming in late here, but I see MacOS and /tmp being at
issue, and it's possible
Apple's weird new permission stuff might be getting triggered
here?
The /tmp directory has weird perms already (prevents users from
accessing each other's tmp files),
and there's all that new lower level permission stuff Apple's
been adding over the last few years,
not just with xattr(), but also with all that new stuff above
and beyond unix permissions that involves
the System Prefs -> Security screen, which gives individual
executables access to specific devices
(like microphones, cameras, etc), which include specific disk
volumes. Perhaps apps need special
access to /tmp?
Anyway, to detect this "new" security stuff, you have to use the
/System/Applications/Utilities/Console
to monitor these errors while the app is running, as such errors
often don't get reported via
traditional unix mechanisms like errno and strerror(), and often
post dialogs asking for access
to things.
So if you suspect weird new Apple security stuff, first run the
Console app (mentioned above),
and hit "Start streaming", then run your app and watch for weird
error messages about your
app in the console.
The console is /very/ chatty, so you have hit "Pause" so you can
scroll around or Copy/Paste
into an editor to find errors/warnings related to your app.
Apple's error messages in this log
about the new privacy stuff are often quite clear about what the
security/privacy problem is,
and it can sometimes be related to how the process was started,
and what limitations are set
in place for that. For instance often the /bin/sh or /bin/bash
has limitations on it that prevent
users from running things from that shell.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/4c9cc8de-09e4-466d-b963-d7cbcb67e39a%40seriss.com.
[ Direct Link to Message ] | |
|
| |
