http://permalink.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://permalink.gmane.org/gmane.lisp.osicat.devel/75 <pre>Hi, I was about to write a portable NATIVE-NAMESTRING function when I noticed the package conflict with OSICAT. Since I don't have texinfo-docstrings I can only guess what's missing so here is a diff: diff --git a/doc/osicat.texinfo b/doc/osicat.texinfo index 53df0bf..05965de 100644 --- a/doc/osicat.texinfo +++ b/doc/osicat.texinfo &lt; at &gt;&lt; at &gt; -99,6 +99,7 &lt; at &gt;&lt; at &gt; &lt; at &gt;include include/macro-osicat-with-temporary-file.texinfo &lt; at &gt;include include/fun-osicat-make-link.texinfo &lt; at &gt;include include/fun-osicat-read-link.texinfo +&lt; at &gt;include include/fun-osicat-native-namestring.texinfo &lt; at &gt;node Users &lt; at &gt;section Users Cheers, max </pre> Max Rottenkolber 2013-05-11T19:15:52 http://permalink.gmane.org/gmane.lisp.osicat.devel/74 <pre> Given that MKDIR is defined via DEFSYSCALL, which is a trivial wrapper around CFFI:DEFCFUN, I suspect this is a CFFI or CCL issue. If you inspect the condition, I suspect you will find an unbound slot. 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 2013-03-27T16:48:14 http://permalink.gmane.org/gmane.lisp.osicat.devel/73 <pre> Yeah, when in doubt I tend to go that way. I thought about this a little bit more; the argument for the no-op behaviour is that it would make unmerge-pathnames work more like the inverse of merge-pathnames, which has no trouble mixing relative and absolute pathnames. But that just makes it clear that unmerge-pathnames is a misnomer, since it only deals with directories and ignores other components. A better name for this function would perhaps reflect its similarities with enough-namestring. Another problem with unmerge-pathnames only taking the directory component into account is that it fails to do the right thing on Windows, where the device component is particularly relevant for this operation. Do you feel like taking a stab at these issues? Cheers, </pre> Luís Oliveira 2012-07-15T01:57:42 http://permalink.gmane.org/gmane.lisp.osicat.devel/72 <pre> So, what you're proposing is that mixing relative pathnames with absolute pathnames turns UNMERGE-PATHNAMES into a no-op. (Your patch only dealt with one such case, where the second pathname was the empty relative pathname #p"".) It seems cleaner to refuse mixing absolute and relative pathnames. Do you have a use case where mixing the two makes sense? </pre> Luís Oliveira 2012-06-29T22:34:58 http://permalink.gmane.org/gmane.lisp.osicat.devel/71 <pre> I think #p"/" should not be treated fundamentally different to #p"foo/". E.g.: (unmerge-pathnames #p"foo/bar/baz" #p"foo/bar/") =&gt; #p"baz" (unmerge-pathnames #p"/foo/bar/baz" #p"foo/bar/") =&gt; #p"/foo/bar/baz" _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs </pre> max< at >mr.gy 2012-06-29T15:24:29 http://permalink.gmane.org/gmane.lisp.osicat.devel/70 <pre> What should it do when it gets a relative pathname? E.g.: #p"foo/bar/". </pre> Luís Oliveira 2012-06-29T00:14:45 http://permalink.gmane.org/gmane.lisp.osicat.devel/69 <pre>Hi, I believe UNMERGE-PATHNAMES should not signal an error if called with #P"" as its second argument. Instead it should return its first argument. I attached a possible bugfix. Cheers, max _______________________________________________ pg-cvs site list pg-cvs&lt; at &gt;common-lisp.net http://common-lisp.net/mailman/listinfo/pg-cvs</pre> max< at >mr.gy 2012-06-22T01:01:15 http://permalink.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://permalink.gmane.org/gmane.lisp.osicat.devel/67 <pre> Sounds like a strange interaction between CCL and CFFI -- could not reproduce on SBCL. Can you provide a tarball that has filenames that cause you trouble? What locale are you using? 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 2012-03-30T14:44:37 http://permalink.gmane.org/gmane.lisp.osicat.devel/66 <pre> Thanks! This one conflicts with the current tree, and the test breaks outside Linux. Cherry-picked and pushed. Cherry-picked and pushed. 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 2012-03-30T14:40:19 http://permalink.gmane.org/gmane.lisp.osicat.devel/65 <pre> Thank you. Pushed ... we'll see if something breaks. (Apropos: attachments generated with "git format-patch -1" are quicker to apply.) 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 2012-03-30T14:22:18 http://permalink.gmane.org/gmane.lisp.osicat.devel/64 <pre> Pushed, thanks! 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 2012-03-30T14:13:11 http://permalink.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://permalink.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://permalink.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://permalink.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://permalink.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://permalink.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://permalink.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://permalink.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://permalink.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 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.lisp.osicat.devel