http://blog.gmane.org/gmane.lisp.osicat.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.lisp.osicat.devel/68 <pre>I get a strange error when calling osicat-posix:mkdir on an already existing directory in Clozure. (osicat-posix:mkdir "/this/directory/exists/" #o777) An error is thrown: -------------------------------------------- #&lt;error printing EEXIST #x1985838E&gt; [Condition of type OSICAT-POSIX:EEXIST] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT-BREAK] Reset this thread 3: [ABORT] Kill this thread Backtrace: 0: (OSICAT-POSIX:POSIX-ERROR 17 NIL OSICAT-POSIX:MKDIR) 1: (CCL::CALL-CHECK-REGS OSICAT-POSIX:MKDIR #P"/home/viper/tmp/bar/" 511) 2: (CCL::CHEAP-EVAL (OSICAT-POSIX:MKDIR (MERGE-PATHNAMES "bar/" "/home/viper/tmp/") 511)) 3: (SWANK::EVAL-REGION "(osicat-posix:mkdir (merge-pathnames \"bar/\" \"/home/viper/tmp/\") #o777)\n") -------------------------------------------- Select restart 1 (abort), another error comes up: -------------------------------------------- Illegal :UTF-8 character starting at position 0. [Condition of typ</pre> Vladimir Sedach 2012-04-15T23:29:46 http://comments.gmane.org/gmane.lisp.osicat.devel/63 <pre> Hi, I added support for the prctl() Linux syscall to Osicat, and made two test-related fixes. The patches are available on my Github Osicat fork [1], more precisely: https://github.com/galdor/osicat/commit/736bb5c10c9c55ed76def0d58da31c1ad1eeff05 https://github.com/galdor/osicat/commit/bede645f2a3d15d825160c7518c295c95bed4271 https://github.com/galdor/osicat/commit/288dc2ee6a6861ea272ea75bb3e346cda6ca85a7 You may be interested in picking them in the official Osicat repository :) [1] https://github.com/galdor/osicat Regards, </pre> Nicolas Martyanoff 2012-02-22T07:29:57 http://comments.gmane.org/gmane.lisp.osicat.devel/62 <pre>It seems walk-directory will skip files and directories whose name is in Unicode, such as Chinese. Is this a bug? Test platform: Mac OS 10.7 Lion, Clozure Common Lisp 1.8 Test Code: (require "asdf") (require "osicat") (defpackage :com.losttemple.zip-db (:use :common-lisp :osicat)) (in-package :com.losttemple.zip-db) (walk-directory (current-directory) #'(lambda (x) (format t "~a~%" (absolute-pathname x))) :test #'(lambda (x) (format t "---~a~%" (absolute-pathname x)) t) :directories :depth-first) (in-package :common-lisp-user) (quit) </pre> Achilles Xu 2012-02-06T09:22:08 http://comments.gmane.org/gmane.lisp.osicat.devel/61 <pre>Clisp doesn't have (posix:getuid) function, instead it uses (posix:uid). Here's small patch to fix it in osicat tests. Timo diff --git a/tests/tests.lisp b/tests/tests.lisp index 2710a8f..7d0c399 100644 --- a/tests/tests.lisp +++ b/tests/tests.lisp &lt; at &gt;&lt; at &gt; -59,6 +59,6 &lt; at &gt;&lt; at &gt; (defun our-getuid () #+sbcl (sb-unix:unix-getuid) #+cmu (unix:unix-getuid) - #+clisp (posix:getuid) + #+clisp (posix:uid) #+allegro (excl.osi:getuid) #-(or sbcl cmu clisp allegro) 0) ; A sane enough default for testing? _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs </pre> Timo Myyrä 2012-01-12T11:20:46 http://comments.gmane.org/gmane.lisp.osicat.devel/60 <pre>Hi, Here's diff to make osicat work on OpenBSD. OpenBSD doesn't define blksize_t and blkcnt_t so define them as 'long'. Not sure if this is correct but seems to work. Neither does OpenBSD have the timer functions so omit them on OpenBSD. The tests need to be tweaked for OpenBSD too, its similar to darwin in this. Testing with other BSD's would be welcome to see if it its needed there as well. The funcall-getpw function seems to handle return values incorrectly. As result it would cause exception on OpenBSD with incorrect entries and not nil value as expected. The fix below works on OpenBSD but could use some testing on other platforms as well. Hopefully gmail won't break the diff. Timo diff --git a/posix/basic-unixint.lisp b/posix/basic-unixint.lisp index 3ee3710..88371ae 100644 --- a/posix/basic-unixint.lisp +++ b/posix/basic-unixint.lisp &lt; at &gt;&lt; at &gt; -286,12 +286,18 &lt; at &gt;&lt; at &gt; (ctype dev "dev_t") (ctype ino "ino_t") -#-windows +#-(or windows openbsd) (progn (ctype nlink "nlink_t") (ctype blksize "blksize_t"</pre> Timo Myyrä 2012-01-08T09:55:44 http://comments.gmane.org/gmane.lisp.osicat.devel/60 <pre>Hi, Here's diff to make osicat work on OpenBSD. OpenBSD doesn't define blksize_t and blkcnt_t so define them as 'long'. Not sure if this is correct but seems to work. Neither does OpenBSD have the timer functions so omit them on OpenBSD. The tests need to be tweaked for OpenBSD too, its similar to darwin in this. Testing with other BSD's would be welcome to see if it its needed there as well. The funcall-getpw function seems to handle return values incorrectly. As result it would cause exception on OpenBSD with incorrect entries and not nil value as expected. The fix below works on OpenBSD but could use some testing on other platforms as well. Hopefully gmail won't break the diff. Timo diff --git a/posix/basic-unixint.lisp b/posix/basic-unixint.lisp index 3ee3710..88371ae 100644 --- a/posix/basic-unixint.lisp +++ b/posix/basic-unixint.lisp &lt; at &gt;&lt; at &gt; -286,12 +286,18 &lt; at &gt;&lt; at &gt; (ctype dev "dev_t") (ctype ino "ino_t") -#-windows +#-(or windows openbsd) (progn (ctype nlink "nlink_t") (ctype blksize "blksize_t"</pre> Timo Myyrä 2012-01-08T09:55:44 http://comments.gmane.org/gmane.lisp.osicat.devel/60 <pre>Hi, Here's diff to make osicat work on OpenBSD. OpenBSD doesn't define blksize_t and blkcnt_t so define them as 'long'. Not sure if this is correct but seems to work. Neither does OpenBSD have the timer functions so omit them on OpenBSD. The tests need to be tweaked for OpenBSD too, its similar to darwin in this. Testing with other BSD's would be welcome to see if it its needed there as well. The funcall-getpw function seems to handle return values incorrectly. As result it would cause exception on OpenBSD with incorrect entries and not nil value as expected. The fix below works on OpenBSD but could use some testing on other platforms as well. Hopefully gmail won't break the diff. Timo diff --git a/posix/basic-unixint.lisp b/posix/basic-unixint.lisp index 3ee3710..88371ae 100644 --- a/posix/basic-unixint.lisp +++ b/posix/basic-unixint.lisp &lt; at &gt;&lt; at &gt; -286,12 +286,18 &lt; at &gt;&lt; at &gt; (ctype dev "dev_t") (ctype ino "ino_t") -#-windows +#-(or windows openbsd) (progn (ctype nlink "nlink_t") (ctype blksize "blksize_t"</pre> Timo Myyrä 2012-01-08T09:55:44 http://comments.gmane.org/gmane.lisp.osicat.devel/59 <pre>Hi, Osicat fails to compile on OpenBSD because of missing defines for blksize_t and blkcnt_t. External process exited with code 1. Command was: "cc" "-m64" "-I/home/zmyrgel/quicklisp/dists/quicklisp/software..." "-fPIC" "-o" "/home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openb..." "/home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openb..." Output was: /home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openbsd-bsd-x64/home/zmyrgel/quicklisp/dists/quicklisp/software/osicat-20110619-git/posix/basic-unixint.c: In function 'main': /home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openbsd-bsd-x64/home/zmyrgel/quicklisp/dists/quicklisp/software/osicat-20110619-git/posix/basic-unixint.c:2041: error: 'blksize_t' undeclared (first use in this function) /home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openbsd-bsd-x64/home/zmyrgel/quicklisp/dists/quicklisp/software/osicat-20110619-git/posix/basic-unixint.c:2041: error: (Each undeclared identifier is reported only once /home/zmyrgel/.cache/common-lisp/sbcl-1.0.54.openbsd-bsd-x64/home/zmy</pre> Timo Myyrä 2012-01-02T12:43:39 http://comments.gmane.org/gmane.lisp.osicat.devel/58 <pre>Hi Osicat developers, Disregard my previous note about problems compiling osicat-posix on 64-bit for 32-bit lispworks. Thing work just fine if you install the 32-bit gcc, and just let it happen! Best regards, Peter _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> Peter Denno 2011-11-27T00:00:54 http://comments.gmane.org/gmane.lisp.osicat.devel/57 <pre>Hi, I ran into a problem compiling osicat-posix under the environment described in the subject line. What I get: [package osicat-posix]; /usr/bin/cc -m32 -I/home/pdenno/quicklisp/dists/quicklisp/software/cffi_0.10.6/ -fPIC -o /home/pdenno/.cache/common-lisp/lw-6.0.1-linux-x86/home/pdenno/quicklisp/dists/quicklisp/software/osicat-20110619-git/posix/basic-unixint /home/pdenno/.cache/common-lisp/lw-6.0.1-linux-x86/home/pdenno/quicklisp/dists/quicklisp/software/osicat-20110619-git/posix/basic-unixint.c External process exited with code 1. Command was: "/usr/bin/cc" "-m32" "-I/home/pdenno/quicklisp/dists/quicklisp/software/..." "-fPIC" "-o" "/home/pdenno/.cache/common-lisp/lw-6.0.1-linux-x86..." "/home/pdenno/.cache/common-lisp/lw-6.0.1-linux-x86..." Output was: /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-suse-linux/4.3/libgcc.a when searching for -lgcc /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: cannot fi</pre> Peter Denno 2011-11-26T22:49:56 http://comments.gmane.org/gmane.lisp.osicat.devel/55 <pre>Hello, the function `open-temporary-file` currently returns a stream and nothing else. Consequently, `with-temporary-file` only exposes a stream to its body. From my understanding it is (intentionally, because streams are an abstraction) not possible to tell what the name of the corresponding temporary file is just by that. Could open-temporary-file be made to return the name of that file as well? I'd like to be able to write code like the following (osicat:with-temporary-file (stream filename) (format stream "some content") (= 0 (sb-ext:process-exit-code (sb-ext:run-program "./test.sh" (list filename))))) In other words, I'd like to pass strings in the form of (temporary) files to a script/program that reads from the file whose name it is passed and use `with-temporary-file` for that. Is that reasonable? Best regards, Elias Pipping _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs </pre> Elias Pipping 2011-09-19T16:40:01 http://comments.gmane.org/gmane.lisp.osicat.devel/45 <pre>I initially neglected to send this register an account w/ osicat-devel and mailed the following exchange to Nikodemus directly with the subject line: "osicat:list-directory vs. cl-fad:list-directory" No doubt Nikodemus has plenty on his plate right now as it is and needn't be solely responsible for fielding this verobisty :) I should have taken the time to register an osicat-devel account. Having done so I am now forwarding a transcript of my previous exchange. -------------- On 12 August 2011 19:46, MON KEY wrote: I noticed today that on SBCL these return differently: (cl-fad:list-directory ".") (osicat:list-directory ".") (cl-fad:list-directory "..") (osicat:list-directory "..") Assuming this is a bug, then i'm pretty sure its origin is around the reliance on osicat:with-directory-iterator. osicat:call-with-directory-iterator binds *d-p-d* to the value of the dir var before setting cwd in the protected form of its unwind-protect. Further up in osicat:call-with-directory-iterator there is a merge </pre> MON KEY 2011-08-12T19:36:23 http://comments.gmane.org/gmane.lisp.osicat.devel/44 <pre>I've created a patch for the missing gr_mem field of cstruct group that fetches the group members properly as a list of strings. Who can I send the patch or where can I get git push rights, alternatively? Alex </pre> Alexander Kahl 2011-07-06T08:42:58 http://comments.gmane.org/gmane.lisp.osicat.devel/42 <pre>Hello, I'm moving a bunch of repositories to github, to make projects more visible, keep track of forks, etc. Unless there are any objections, I can put osicat there as well as an organization and add current committers as owners. Cheers, </pre> Luís Oliveira 2011-05-28T20:03:34 http://comments.gmane.org/gmane.lisp.osicat.devel/40 <pre>For some reason the repository had grown a bare = false which broke pushing. Before I managed to figure out what was wrong, I ended up replacing the whole repo with a new clone. Should be OK now. Cheers, -- nikodemus _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs </pre> Nikodemus Siivola 2011-05-28T09:17:21 http://comments.gmane.org/gmane.lisp.osicat.devel/39 <pre>Hi, Attached is a patch for a WITH-TEMPORARY-DIRECTORY macro. (defmacro with-temporary-directory ((directory &amp;key (pathspec *temporary-directory*)) &amp;body body) "Within the lexical scope of the body, DIRECTORY is bound to a newly created temporary directory. When BODY exits, the created directory (and all its containing files) are deleted before the value of the last form in BODY is returned. The value of PATHSPEC determines the location and prefix of the temporary directory. The PATHNAME-DIRECTORY component of PATHSPEC determines the location in which the temporary directory is to be created. A non null PATHNAME-NAME of PATHSPEC will be used as a prefix of the temporary directory. " ...) Thanks Mark _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> Mark Cox 2011-01-19T08:51:25 http://comments.gmane.org/gmane.lisp.osicat.devel/38 <pre>In osicat's fd-streams.lisp, there is a function, make-fd-stream. The sbcl version ignores the pathname parameter, but I'm not sure why. If you set the pathname parameter in the stream, you can then recover the pathname from the stream later on. And if you don't unlink tmp files immediately after creation, you can do stuff like this: (let* ((stream (open-temporary-file :no-unlink t)) (fname (namestring (pathname stream)))) (write-data-to-temp-file stream) (close stream) (do-shell-command-on-temp-file fname) (nix:unlink fname)) Sure, that's not the prettiest thing you'll ever do, but it works pretty well when you need it. If you want osicat to support that use case, I offer a couple small patches that don't ignore pathname in make-fd-stream on sbcl and that allow specifying (:no-unlink t) when opening temporary files. Thanks much. _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> James Vasile 2010-12-18T04:56:00 http://comments.gmane.org/gmane.lisp.osicat.devel/35 <pre>I pushed a few additions used by qthemlock to the Osicat master -- mostly termios related. Even if they qthemlock should move away from Osicat, they still belong appropriately to NIX. Cheers, -- Nikodemus _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs </pre> Nikodemus Siivola 2009-12-22T18:11:29 http://comments.gmane.org/gmane.lisp.osicat.devel/34 <pre>_______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> madnificent< at >gmail.com 2009-11-11T11:56:49 http://comments.gmane.org/gmane.lisp.osicat.devel/33 <pre>_______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> Brit Butler 2009-11-03T21:04:56 http://comments.gmane.org/gmane.lisp.osicat.devel/30 <pre> When I create a custom core the location of libosicat.so is hard-coded in the binary. Osicat should instruct CFFI/SB-ALIEN to load this library with :DONT-SAVE T to prevent saving a fixed path. Leslie </pre> Leslie P. Polzer 2009-08-23T12:29:30 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.lisp.osicat.devel