Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
TK as framework on Mojave (macOS10.14)
103 views
Skip to first unread message
Nicolas
Nov 6, 2018, 10:28:05 AM11/6/18
to
not sure where to post this....
I got errors like the following one when using Tk8.6.9_rc3 on mojave
error: invalid kernel:
** OpenCL Error Notification: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: build program driver returned (-3) **
** OpenCL Error Notification: OpenCL Warning : clBuildProgram failed: could not build program for 0xffffffff (Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz) (err:-3) **
** OpenCL Error Notification: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:
No kernels or only kernel prototypes found when build executable.
**
Native OpenCL program build failed:
No kernels or only kernel prototypes found when build executable.Kernel source code =
#define writeImage(c, p, _dc) write_imagef(_outputTexture, (int2)p, c)
#define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
#define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
#define writeCoord(_dc) (float2)_writeLoc
thank you for any pointer.
best regards,
Nicolas
I got errors like the following one when using Tk8.6.9_rc3 on mojave
error: invalid kernel:
** OpenCL Error Notification: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: build program driver returned (-3) **
** OpenCL Error Notification: OpenCL Warning : clBuildProgram failed: could not build program for 0xffffffff (Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz) (err:-3) **
** OpenCL Error Notification: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:
No kernels or only kernel prototypes found when build executable.
**
Native OpenCL program build failed:
No kernels or only kernel prototypes found when build executable.Kernel source code =
#define writeImage(c, p, _dc) write_imagef(_outputTexture, (int2)p, c)
#define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
#define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
#define writeCoord(_dc) (float2)_writeLoc
thank you for any pointer.
best regards,
Nicolas
Christian Gollwitzer
Nov 6, 2018, 11:52:39 AM11/6/18
to
Am 06.11.18 um 16:28 schrieb Nicolas:
Are you sure that this error message comes from Tk? That is highly
unlikely - it is an error while compiling an OpenCL kernel. Tk in its
basic form does not use OpenCL.
BTW, with Mojave Apple has deprecated OpenCL in favour of Metal, which
is a shame. :( I will consider a migration path away from Apple.
Christian
unlikely - it is an error while compiling an OpenCL kernel. Tk in its
basic form does not use OpenCL.
BTW, with Mojave Apple has deprecated OpenCL in favour of Metal, which
is a shame. :( I will consider a migration path away from Apple.
Christian
Nicolas
Nov 6, 2018, 2:50:03 PM11/6/18
to
thank you for your answer.
yes, I'm pretty sure it comes from Tk as it's the only UI lib I'm using.
I can investigate more but this message raise when I call tk_getSaveFile
++
Christian Gollwitzer
Nov 7, 2018, 3:27:47 AM11/7/18
to
Am 06.11.18 um 20:50 schrieb Nicolas:
these functions, nor to OpenCL at all - it must come from something
else, or maybe a dependent library
> I can investigate more but this message raise when I call tk_getSaveFile
When you run this, an instance of Finder opens. I can imagine that you
have an extension which tries to display something in the Finder window.
Can you try open a program at the command line which features a file
open dialog, e.g.
open -n -a TextEdit
and open a file dialog? Or have a look into the log window
(console.app). I can imagine that the error messages come with every
file dialog, but that you simply don't see them in other programs,
because they run without a terminal.
Christian
> Le mardi 6 novembre 2018 17:52:39 UTC+1, Christian Gollwitzer a écrit :
>> Am 06.11.18 um 16:28 schrieb Nicolas:
>> Am 06.11.18 um 16:28 schrieb Nicolas:
>>> #define writeImage(c, p, _dc) write_imagef(_outputTexture, (int2)p, c)
>>> #define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
>>> #define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
>>> #define writeCoord(_dc) (float2)_writeLoc
>>
>> Are you sure that this error message comes from Tk? That is highly
>> unlikely - it is an error while compiling an OpenCL kernel. Tk in its
>> basic form does not use OpenCL.
>
>>> #define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
>>> #define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
>>> #define writeCoord(_dc) (float2)_writeLoc
>>
>> Are you sure that this error message comes from Tk? That is highly
>> unlikely - it is an error while compiling an OpenCL kernel. Tk in its
>> basic form does not use OpenCL.
>
> thank you for your answer.
> yes, I'm pretty sure it comes from Tk as it's the only UI lib I'm using.
I just double checked, the Tk source code of 8.6.9rc3 does not refer to
> yes, I'm pretty sure it comes from Tk as it's the only UI lib I'm using.
these functions, nor to OpenCL at all - it must come from something
else, or maybe a dependent library
> I can investigate more but this message raise when I call tk_getSaveFile
have an extension which tries to display something in the Finder window.
Can you try open a program at the command line which features a file
open dialog, e.g.
open -n -a TextEdit
and open a file dialog? Or have a look into the log window
(console.app). I can imagine that the error messages come with every
file dialog, but that you simply don't see them in other programs,
because they run without a terminal.
Christian
Nicolas
Nov 7, 2018, 4:43:18 AM11/7/18
to
Hi Christian,
Le mercredi 7 novembre 2018 09:27:47 UTC+1, Christian Gollwitzer a écrit :
> Am 06.11.18 um 20:50 schrieb Nicolas:
> > Le mardi 6 novembre 2018 17:52:39 UTC+1, Christian Gollwitzer a écrit :
> >> Am 06.11.18 um 16:28 schrieb Nicolas:
>
> >>> #define writeImage(c, p, _dc) write_imagef(_outputTexture, (int2)p, c)
> >>> #define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
> >>> #define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
> >>> #define writeCoord(_dc) (float2)_writeLoc
> >>
> >> Are you sure that this error message comes from Tk? That is highly
> >> unlikely - it is an error while compiling an OpenCL kernel. Tk in its
> >> basic form does not use OpenCL.
>
> >
> > thank you for your answer.
> > yes, I'm pretty sure it comes from Tk as it's the only UI lib I'm using.
>
> I just double checked, the Tk source code of 8.6.9rc3 does not refer to
> these functions, nor to OpenCL at all - it must come from something
> else, or maybe a dependent library
>
I've checked also and indeed did not find any reference to OpenCL...
I must have done something wrong because the error doesn't raise anymore...
> > I can investigate more but this message raise when I call tk_getSaveFile
>
> When you run this, an instance of Finder opens. I can imagine that you
> have an extension which tries to display something in the Finder window.
> Can you try open a program at the command line which features a file
> open dialog, e.g.
>
> open -n -a TextEdit
>
> and open a file dialog? Or have a look into the log window
> (console.app). I can imagine that the error messages come with every
> file dialog, but that you simply don't see them in other programs,
> because they run without a terminal.
exact, each time an openFile window is raising I got the following line (either from my app or the open -n -a TextEdit command):
Nov 7 09:41:49 mac-de-nicolas TextEdit[16667]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Nov 7 09:41:50 mac-de-nicolas com.apple.appkit.xpc.openAndSavePanelService[16669]: objc[16669]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffab0f41d0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10aa3adc8). One of the two will be used. Which one is undefined.
and regarding tk_getSaveFile when I hit Save after setting the filename everything is fine , but if I hit Enter, my app crash everytime and console is not very helpful:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 Tk 0x000000010607dfb8 0x105f2c000 + 1384376
1 Tk 0x000000010607d98d 0x105f2c000 + 1382797
2 Tk 0x000000010607545b 0x105f2c000 + 1348699
3 Tk 0x0000000106088eee 0x105f2c000 + 1429230
4 Tcl 0x0000000105e5c851 Tcl_DoOneEvent + 497
Nicolas
>
> Christian
Le mercredi 7 novembre 2018 09:27:47 UTC+1, Christian Gollwitzer a écrit :
> Am 06.11.18 um 20:50 schrieb Nicolas:
> > Le mardi 6 novembre 2018 17:52:39 UTC+1, Christian Gollwitzer a écrit :
> >> Am 06.11.18 um 16:28 schrieb Nicolas:
>
> >>> #define writeImage(c, p, _dc) write_imagef(_outputTexture, (int2)p, c)
> >>> #define writeImagePlane(c, p, _dc) write_imagef(_outputTexturePlane, (int2)p, c)
> >>> #define writePixel(r, g, b, a, p, _dc) write_imagei(_outputTexture, (int2)p, (int4)(r,g,b,a))
> >>> #define writeCoord(_dc) (float2)_writeLoc
> >>
> >> Are you sure that this error message comes from Tk? That is highly
> >> unlikely - it is an error while compiling an OpenCL kernel. Tk in its
> >> basic form does not use OpenCL.
>
> >
> > thank you for your answer.
> > yes, I'm pretty sure it comes from Tk as it's the only UI lib I'm using.
>
> I just double checked, the Tk source code of 8.6.9rc3 does not refer to
> these functions, nor to OpenCL at all - it must come from something
> else, or maybe a dependent library
>
I must have done something wrong because the error doesn't raise anymore...
> > I can investigate more but this message raise when I call tk_getSaveFile
>
> When you run this, an instance of Finder opens. I can imagine that you
> have an extension which tries to display something in the Finder window.
> Can you try open a program at the command line which features a file
> open dialog, e.g.
>
> open -n -a TextEdit
>
> and open a file dialog? Or have a look into the log window
> (console.app). I can imagine that the error messages come with every
> file dialog, but that you simply don't see them in other programs,
> because they run without a terminal.
Nov 7 09:41:49 mac-de-nicolas TextEdit[16667]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Nov 7 09:41:50 mac-de-nicolas com.apple.appkit.xpc.openAndSavePanelService[16669]: objc[16669]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffab0f41d0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10aa3adc8). One of the two will be used. Which one is undefined.
and regarding tk_getSaveFile when I hit Save after setting the filename everything is fine , but if I hit Enter, my app crash everytime and console is not very helpful:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 Tk 0x000000010607dfb8 0x105f2c000 + 1384376
1 Tk 0x000000010607d98d 0x105f2c000 + 1382797
2 Tk 0x000000010607545b 0x105f2c000 + 1348699
3 Tk 0x0000000106088eee 0x105f2c000 + 1429230
4 Tcl 0x0000000105e5c851 Tcl_DoOneEvent + 497
Nicolas
>
> Christian
0 new messages