From: Rick T. <ta...@ui...> - 2005-07-03 13:26:35
|
im working on an ffi to portmidi, when i load it on OSX i get some style warnings that are triggered by my file but are not actually part of my code. any ideas why this is happening or how to stop the messages from appearing? these messages do not appear on linux. [...] ; Compiling "src/portmidi.lisp" ; Loading "bin/sbcl_0.9.0_darwin-powerpc/portmidi.fasl" STYLE-WARNING: Undefined alien: "fdatasync" STYLE-WARNING: Undefined alien: "lchown" STYLE-WARNING: Undefined alien: "getresuid" STYLE-WARNING: Undefined alien: "setfsuid" STYLE-WARNING: Undefined alien: "setresuid" STYLE-WARNING: Undefined alien: "getresgid" STYLE-WARNING: Undefined alien: "setfsgid" STYLE-WARNING: Undefined alien: "setresgid" [...] |
From: Nikodemus S. <nik...@ra...> - 2005-07-03 13:46:33
|
On Sun, 3 Jul 2005, Rick Taube wrote: > im working on an ffi to portmidi, when i load it on OSX i get some style > warnings that are triggered by my file but are not actually part of my code. > any ideas why this is happening or how to stop the messages from appearing? > these messages do not appear on linux. These are most likely from SB-POSIX, which includes these, though they don't seem to be available on your system. However, SB-POSIX should detect that they are missing at compile-time, and not complain later. Does (require :sb-posix) in the repl result in the same barrage? Does the same happen with SBCL 0.9.2? What OS X version is this? Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |
From: Rick T. <ta...@ui...> - 2005-07-03 14:08:49
|
thank you for the quick reply! > Does (require :sb-posix) in the repl result in the same barrage? no: * (require :sb-posix) ("SB-POSIX" "SB-GROVEL" "ASDF") > Does the same happen with SBCL 0.9.2? i just have the binary 090 release - ill download the tarball now and try to build and test. > What OS X version is this? Im running OSX version 10.3.9. uname info is: $ uname -a Darwin galen.local 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc --rick |
From: David L. <dav...@li...> - 2005-07-03 13:49:28
|
Quoting Rick Taube (ta...@ui...): > im working on an ffi to portmidi, when i load it on OSX i get some > style warnings that are triggered by my file but are not actually part > of my code. [...] > STYLE-WARNING: Undefined alien: "fdatasync" When compiled with linkage-table support, SBCL checks references to foreign symbols it has seen after loading a shared object. I would guess that the above definitions are from sb-posix, which might declare these foreign functions even they they are not supported by the operating system. Since the system has no way to map symbols to libraries before having found the symbol in a certain library, it has to check all of them every time. Perhaps more control could be offered to the caller of load-shared-object by adding an argument specifying the symbols to look for. For some user programs it might even be convenient to not update the linkage table at all when loading a shared library if a function was documented that lets users search for a specific symbol in either all loaded libraries or a specific library if and when they need it. (Currently there is no documented way to have functions with the name in different library and calling a specific one of those.) In practise though, I just wrap a (handler-bind ((style-warning #'muffle-warning)) ...) around my calls to load-foreign-object to suppress the warnings. d. |
From: Nikodemus S. <nik...@ra...> - 2005-07-03 14:20:59
|
On Sun, 3 Jul 2005, Rick Taube wrote: > i just have the binary 090 release - ill download the tarball now and try to > build and test. No need, actually: I found the bug -- the detection I referred to is broken. I'll commit a fix shortly. Temporary workarounds: * (require :sb-posix) instead of plain ASDF. * HANDLER-BIND & MUFFLE-WARNING as suggested by David. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |
From: Rick T. <ta...@ui...> - 2005-07-03 14:47:12
|
> No need, actually: I found the bug -- the detection I referred to is > broken. I'll commit a fix shortly. thank you! while im on the subject of MIDI (well, the lib was "libportmidi.dylib" after all :)) i have to poll for incoming messages and native threads would really help out with this. more importantly native threads might also allow me to do something ive been hoping for for about 15 years: scheduling real-time musical processes in lisp to run concurrently with musical performance input so it could all evolve in real time. with the slime related thread discussion the past few weeks ive seen hopeful signs for this but im not really sure what the state of affairs is: 1 is a high-level api to native threads in the works for sbcl? 2 if so, will it be available on osx and linux? --rick On Jul 3, 2005, at 9:20 AM, Nikodemus Siivola wrote: > On Sun, 3 Jul 2005, Rick Taube wrote: > >> i just have the binary 090 release - ill download the tarball now and >> try to build and test. > > No need, actually: I found the bug -- the detection I referred to is > broken. I'll commit a fix shortly. > > Temporary workarounds: > > * (require :sb-posix) instead of plain ASDF. > > * HANDLER-BIND & MUFFLE-WARNING as suggested by David. > > Cheers, > > -- Nikodemus Schemer: "Buddha is small, clean, and > serious." > Lispnik: "Buddha is big, has hairy armpits, and > laughs." |
From: Brian M. <br...@ma...> - 2005-07-04 01:34:17
|
On Jul 3, 2005, at 9:47 AM, Rick Taube wrote: >> No need, actually: I found the bug -- the detection I referred to >> is broken. I'll commit a fix shortly. >> > > thank you! while im on the subject of MIDI (well, the lib was > "libportmidi.dylib" after all :)) i have to poll for incoming > messages and native threads would really help out with this. more > importantly native threads might also allow me to do something ive > been hoping for for about 15 years: scheduling real-time musical > processes in lisp to run concurrently with musical performance > input so it could all evolve in real time. with the slime related > thread discussion the past few weeks ive seen hopeful signs for > this but im not really sure what the state of affairs is: > 1 is a high-level api to native threads in the works for sbcl? There is a sbcl-devel thread about thread objects and the thread API which details some of the threads hackers' current plans along those lines. > 2 if so, will it be available on osx and linux? Linux definitely. It depends on what you mean by "OS X", though. Our threading support requires the generational garbage collector and that isn't ported to PowerPC; nor is it a trivial task. I would just as soon familiarize myself with the goings-on in the x86 port and runtime so that I can port to Darwin on x86. To that end I'm going to try to finish the Solaris x86 runtime (it looks like there was an issue with the control stack guard page), port to Solaris x86-64, and work on threads for both. The long and short of it is that because we'll have the generational collector available on x86 OS X, I hope that we'll have threads too. > --rick -- Brian Mastenbrook br...@ma... http://www.iscblog.info/ |
From: Nikodemus S. <nik...@ra...> - 2005-07-05 12:29:23
|
On Sun, 3 Jul 2005, Nikodemus Siivola wrote: > On Sun, 3 Jul 2005, Rick Taube wrote: > >> i just have the binary 090 release - ill download the tarball now and try >> to build and test. > > No need, actually: I found the bug -- the detection I referred to is broken. > I'll commit a fix shortly. Should be fixed in 0.9.2.26. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |