osicat-devel

osicat-devel@common-lisp.net

61 discussions

[pg-cvs] Patch for getgrnam / getgrgid members
by Alexander Kahl 06 Jul '11

06 Jul '11

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 -- Alexander Kahl █▉ www: http://fsfe.org FSFE Fellow █▉█▉█▉ e-mail: e-user(a)fsfe.org Lambda Hacker ▉▉ xmpp: e-user(a)jabber.fsfe.org

1 0

[pg-cvs] Using github
by Luís Oliveira 28 May '11

28 May '11

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, -- Luís Oliveira http://r42.eu/~luis/

2 1

Re: [pg-cvs] osicat patch for interval timers
by Nikodemus Siivola 28 May '11

28 May '11

On 27 May 2011 23:33, Robert Brown <brown(a)google.com> wrote: > Here is a patch to osicat that adds support for Posix interval timers. Applied and pushed, thank you! Cheers, -- Nikodemus

1 0

[pg-cvs] new old new repository
by Nikodemus Siivola 28 May '11

28 May '11

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

1 0

[pg-cvs] Adding WITH-TEMPORARY-DIRECTORY
by Mark Cox 19 Jan '11

19 Jan '11

Hi, Attached is a patch for a WITH-TEMPORARY-DIRECTORY macro. (defmacro with-temporary-directory ((directory &key (pathspec *temporary-directory*)) &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

1 0

[pg-cvs] patch: no-unlink parameter for temporary file creation
by James Vasile 18 Dec '10

18 Dec '10

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.

1 0

Re: [pg-cvs] CFFI fork_and_exec for Hemlock/iolib
by Luís Oliveira 23 Dec '09

23 Dec '09

[Added osicat-devel to the Cc: list.] On Tue, Dec 22, 2009 at 11:17 AM, Nikodemus Siivola <nikodemus(a)random-state.net> wrote: > Assuming someone had the time to do it, would all involved be happy if > iolib and osicat shared a low-level POSIX/BSD/Linux API with minimal > deps, or are there reasons not to use a shared layer? Initially the new Osicat stuff was in a library called CL-POSIX. However it turns out to be useful to share a bit of code between posix, windows, mach, etc. In particular, it's nice to have e.g. posix and windows errors inherit from a common condition. Thus OSICAT-SYS was born, that includes code shared by OSICAT-POSIX, OSICAT-WINDOWS and OSICAT-MACH. OSICAT is then implemented on top of these. Splitting all these into different projects didn't seem worth the trouble at the time. Still doesn't seem worth the trouble right now, what do you think? > Also related to both Osicat and iolib: neither includes the name of > the failing syscall in the error conditions they signal. I don't quite > understand the way the CFFI type system works to provide these, but > assuming you do... would it be hard to add it in? It was fairly straightforward: OSICAT> (handler-case (nix:mkdir "/" 0) (nix:eisdir (c) ; OSX signals this funny error (nix::posix-error-syscall c))) OSICAT-POSIX:MKDIR Is this what you were looking for? If yes, I'll clean up the attached patch and commit it to Osicat. -- Luís Oliveira http://r42.eu/~luis/

2 1

[pg-cvs] osicat-posix additions
by Nikodemus Siivola 22 Dec '09

22 Dec '09

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

1 0

[pg-cvs] issue: mmap returns a pointer
by madnificent＠gmail.com 11 Nov '09

11 Nov '09

Hello osicat-devel Whilst getting help from John Fremlin for manardb, an issue with osicat arose. Apparently osicat-posix assumes that the return value from mmap is an int when it is a pointer. He noted that mremap is broken too. a backtrace containing the result: CL-USER> (manardb:use-mmap-dir "/tmp/manardb/" :if-does-not-exist :create) The value -134270976 is not of type (UNSIGNED-BYTE 64). [Condition of type TYPE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {1003249DB1}>) Backtrace: 0: (OSICAT-POSIX:MMAP #.(SB-SYS:INT-SAP #X00000000) 4096 3 1 4 0) 1: (MANARDB::MTAGMAP-OPEN #<MANARDB::MTAGMAP >)[:EXTERNAL] 2: (MANARDB:OPEN-ALL-MMAPS) John Fremlin made me fix the bug by evaluating the following code in osicat-posix: (DEFCFUN ("mmap_cffi_wrap" MMAP :CONVENTION :CDECL :LIBRARY :DEFAULT) (ERRNO-WRAPPER :UNSIGNED-LONG :ERROR-PREDICATE (LAMBDA (P) (= P MAP-FAILED)) :RETURN-FILTER MAKE-POINTER) (START :POINTER) (LENGTH SIZE) (PROT :INT) (FLAGS :INT) (FD FILE-DESCRIPTOR-DESIGNATOR) (OFFSET OFF)) cheers, the madnificent

1 0

[pg-cvs] ECL Build Problems
by Brit Butler 03 Nov '09

03 Nov '09

Dear osicat-devs, I am presently unable to (require 'osicat) on ECL Head. There is a complete log of the (require ...) output at http://redlinernotes.com/docs/osicat.txt. Here's the short version: There is some sort of problem with posix/basic-unixint.c. My understanding is that ECL invokes GCC to try and produce a .o file and that compilation seems to fail. I get no output explaining why. Later ECL seems to try to link against basic-unixint.o which was never created and it complains of a truncated file. I may be misreading the output. I would love to be able to use Osicat with ECL. Is there some way I can provide more information or otherwise help rectify this? Regards, Brit Butler

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

osicat-devel