Re: [fltk.coredev] Re: FLTK 1.3.6 Release Candidate 1 is now available for download and testing

GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
Previous Message ]New Message | Reply ]Next Message ]

Re: Re: FLTK 1.3.6 Release Candidate 1 is now available for download and testing Albrecht Schlosser 02:15 May 02 top right image
On 5/2/21 6:54 AM Manolo wrote:

Le samedi 1 mai 2021 à 17:35:45 UTC+2, Albrecht Schlosser a écrit :

    On 5/1/21 4:57 PM Manolo wrote:

     > I have the problem after configure + make, but no problem after
    CMake +
     > make.
     > Very strange.

The error occurs after I downloaded the FLTK source tar archive with Firefox, unfold the archive
and build FLTK. The error symptom is a popup window saying
"Blocks is damaged and can't be opened.
Firefox downloaded this file on …"

If I git clone, git checkout branch-1.3 and build with configure : NO ERROR!

Yes, I see this too.

If I copy the dir from my CMake-based build, _empty it completely_, and then fill it with the content of from my firefox+configure build : NO ERROR Thus, the difference in Info.plist between CMake and configure builds is not the culprit.

I made a similar test: in the <firefox-download> folder I removed test/ and Info.plist, then replaced Info.plist with the Git version and built again (after also removing the blocks wrapper script). After these steps I could open with the Finder.

Thus , the status "I'm suspect, I was downloaded from internet" seems transferred from the tar archive all the way to the directory and to block launching these 3 apps.

In their help info in the message popping up they say it has to do with security and that you should control-click the app and click open to run it. But that doesn't work for me, it just doesn't change anything. See attached open_app_help.txt.

Another observation: when I type in the FLTK root dir:

  open test/

I get a weird error message (attached).

I can still run the executable if I use the wrapper script, like on the commandline:


Really CRAZY!

FTR: I tried to edit Info.plist before building so it gets (maybe) another status, time stamp, whatever, but this didn't help either.

Solution/workaround: drop configure/make build, use CMake instead! ;-)

You know much more about macOS, do you have any other ideas how to solve this?

Mike (Sweet), if you are reading this, do you have any more info/ideas how to work around this "security" issue?

You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit
The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10826 "kLSNoLaunchPermissionErr: User doesn't have permission to launch the app (managed networks)" UserInfo={_LSFunction=_LSLaunchWithRunningboard, _LSLine=2539, NSUnderlyingError=0x14bf1aa50 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x14bf1b450 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 111}}}}}
Open an app by overriding security settings

You can open an app that isn’t allowed to open by manually overriding the settings in Security & Privacy preferences.

In the Finder  on your Mac, locate the app you want to open.

Most apps can be found in the Applications folder.

Control-click the app icon, then choose Open from the shortcut menu.

Click Open.

The app is saved as an exception to your security settings, and you can open it in the future by double-clicking it, just as you can any authorised app.
Direct Link to Message ]
bottom left image   bottom right image
Previous Message ]New Message | Reply ]Next Message ]

Comments are owned by the poster. All other content is copyright 1998-2021 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to ''.