February 2011 - cffi-devel - mailman3.common-lisp.net

[cffi-devel] Digitool MCL support for CFFI (was Re: [info-mcl] ? cffi)
by Chun Tian (binghe) 10 Mar '12

10 Mar '12

Hi, CFFI developers Digitool MCL was a old&famous Common Lisp implementation on PPC Mac OS. Recently it was ported into Intel Mac OS X by running in Rosetta (a PPC emulator by Apple). So there're people still using this platform even when Clozure CL is a better choice. Attach is two patches, one is a CFFI MCL support patch made by James Anderson, the other is a trivial patch for MCL support of trivial-features made by me. With these two patch, CFFI can now be loaded into Digitool MCL. This work seems work with James' own project which is based on CFFI. But CFFI-TESTS cannot run at this time, because ASDF:RUN-SHELL-COMMAND doesn't support MCL (I don't know how to fix this right now). IOlib also cannot work in MCL because Gray Streams wasn't supported by MCL yet ... However, I hope CFFI maintainer could merge this patch and let other MCL users help improving exist work. Chun Tian (binghe) 在 2010-9-28，06:41， james anderson 写道： > good morning; > > i have worked out enough of a cffi-mcl to be able to accomplish the immediate goal - to use the cl-zmq zeromq ffi binding.[1] > in case someone wants to carry it further, it's posted along with a mcl-compatible zmq version,[2] which eliminates un-ported dependencies. > > --- > [1] : http://repo.or.cz/w/cl-zmq.git > [2] : http://github.com/lisp/de.setf.zeromq > > On 2010-09-22, at 08:29 , Chun Tian (binghe) wrote: > >> I've read these documents. MCL 4.0's FFI seems based on the function "define-entry-point" which then depends on "ppc-ff-call", both of them are still available in MCL 5.x, and the related MCL source code is "lib/deftrap.lisp", which was last modified in 2005. >> >> However, I think "define-entry-point" is not the preferred way any more: >> >> ; Change log >> ; >> ; put back define-entry-point and things it depends on - though MCL doesn't use it users may >> ; ------ 5.2b2 >> >> I think CFFI people, if want to support MCL, should research "deftrap.lisp" and figure out the preferred way to do the work. But for me, a USOCKET maintainer, I'd like to use this interface directly to implement UDP networking, which was lack from OpenTransport. >> >> --binghe >> >> 在 2010-9-22，13:30， james anderson 写道： >> >>> there are two sources. >>> >>> if you go to ftp.clozure.com, you will find the 5.2 release and a copy of the documentation for 4.0. >>> i know of no revised documentation for 5.2. other than that, there is always the source. >>> i believe 5.2 has a very different calling mechanism then 4.0, as it uses a different os x facility to manage foreign libraries. >>> >>> the biggest '?' is turning off the gc for the dynamic extent of any foreign calls which pass lisp data. i do not know if that is possible in mcl, but it could be faked by moving the data to/from temporary external storage just to get it working. >>> two little question marks are the data type size calculations and the call-back protocol. >>> since the source is there, there's nothing stopping me from adapting the clozure-specific code to work in mcl. >>> i was just hoping to avoid having to wrap my head around those bits. >>> >>> >>> On 2010-09-22, at 04:45 , Chun Tian (binghe) wrote: >>> >>>> Never know how to do FFI in Digitool MCL ... Where can I find some API documents? >>>> >>>> --binghe >>>> >>>> 在 2010-9-22，05:36， james anderson 写道： >>>> >>>>> good morning; >>>>> >>>>> has anyone ported cffi to mcl? >>>>> >>>>> >>>>> _______________________________________________ >>>>> info-mcl mailing list >>>>> info-mcl(a)clozure.com >>>>> http://clozure.com/mailman/listinfo/info-mcl >>>> >>>> _______________________________________________ >>>> info-mcl mailing list >>>> info-mcl(a)clozure.com >>>> http://clozure.com/mailman/listinfo/info-mcl >>> >>> _______________________________________________ >>> info-mcl mailing list >>> info-mcl(a)clozure.com >>> http://clozure.com/mailman/listinfo/info-mcl >> >> _______________________________________________ >> info-mcl mailing list >> info-mcl(a)clozure.com >> http://clozure.com/mailman/listinfo/info-mcl > > _______________________________________________ > info-mcl mailing list > info-mcl(a)clozure.com > http://clozure.com/mailman/listinfo/info-mcl

2 3

[cffi-devel] trivial-features, CLX and SBCL mutual incompatibility
by Cyrus Harmon 13 Mar '11

13 Mar '11

Forgive me if you've heard me rant about this before, but there is a mutual incompatibility between CLX, trivial-features (which, for me at least, gets pulled in whenever I try to use CFFI) and SBCL. The problem is that trivial-features puts :little-endian on *features* and CLX has the following code in defdeps.lisp: #+(or lispm vax little-endian Minima) (eval-when (eval compile load) (pushnew :clx-little-endian *features*)) These old-style eval-when conditions cause SBCL to issue a warning, which causes ASDF to stop compiling CLX. There are many workarounds to this, such as loading CLX before CFFI and there are many possible fixes (such as making SBCL less pedantic or making ASDF not stop on warnings of this kind, etc...) But it seems to me that either fixing the CLX source code such that it is more tolerant of SBCL's pedantry or, alternatively, picking less common names for the *features* in trivial-features would be a good thing. I don't really have a preference, but it would be nice if the CLX and trivial-features maintainers would play nice with each other such that, at least when using SBCL, one can load trivial-features and then CFFI. I'm certainly open to other suggestions, but I've grown tired of working around this particular problem. thanks, Cyrus

2 4

[cffi-devel] Memory limit when using with-foreign-pointer?
by Carlo Hamalainen 24 Feb '11

24 Feb '11

Hi, I have a small test program that tries to allocate 100Mb and then say hello: ;;;;;;;;;;;;;;;; start of malloc-test.lisp ;;;;;;;;;;;; (asdf:oos 'asdf:load-op :cffi) (defpackage :malloc-test (:use :common-lisp :cffi)) (in-package :malloc-test) ; Attempt to malloc 100Mb of memory and say hello (with-foreign-pointer (data (* 100 1048576 (foreign-type-size :char))) (print "hello")) ;;;;;;;;;;;;;;;; end of malloc-test.lisp ;;;;;;;;;;;;; But when I run it using SBCL on Ubuntu 10.10 32bit, it complains about some value not being of type (MOD 536870909). Is this a deliberate limit on the part of CFFI or SBCL? If so where can I adjust this limit? $ sbcl This is SBCL 1.0.40.0.debian, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (load "malloc-test.lisp") ; loading system definition from /usr/share/common-lisp/systems/cffi.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM CFFI {ADD22C1}> as CFFI ; loading system definition from /usr/share/common-lisp/systems/babel.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM BABEL {B2CB081}> as BABEL ; loading system definition from /usr/share/common-lisp/systems/alexandria.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :ALEXANDRIA {B4AF1B1}> as ALEXANDRIA ; loading system definition from ; /usr/share/common-lisp/systems/trivial-features.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM TRIVIAL-FEATURES {ABBB251}> as TRIVIAL-FEATURES debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread" RUNNING {AACA871}>: The value 838860800 is not of type (MOD 536870909). Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. ((LAMBDA ())) 0] Thanks, -- Carlo Hamalainen http://carlo-hamalainen.net

2 3

[cffi-devel] Groveller bitfield support
by Nicolas Martyanoff 11 Feb '11

11 Feb '11

Hi, On 2010-04-30 a patch was submitted to the cffi-devel mailing-list (http://www.mail-archive.com/cffi-devel@common-lisp.net/msg01820.html) adding support for bitfield in the groveller. On 2010-05-01, a ticket was created about this patch on launchpad (https://bugs.launchpad.net/cffi/+bug/622338) Recently, I asked Stelian Ionescu on #lisp if it was possible to apply the patch to the cffi trunk, and the answer seemed positive. Is there something that prevents committing this patch ? I use it in three different personal projects, it works. If the people which manage the git repository don't have the time (for the last 10 months…) to apply a trivial patch (1 minute top), would they consider giving a commit bit to people that can ? Thank you, -- Nicolas Martyanoff http://codemore.org khaelin(a)gmail.com

3 7

[cffi-devel] CLISP with CFFI for Mac OS X
by Andrew Pennebaker 06 Feb '11

06 Feb '11

Hello, I am a budding Common Lisper. I was working on a cl-mechanize<https://github.com/joachifm/cl-mechanize>script to fill out an HTML form when I noticed that one of cl-mechanize's dependencies, cl+ssl <http://common-lisp.net/project/cl-plus-ssl/>, depends on CFFI. When I try to load cl-mechanize, which loads drakma, which loads cl+ssl, I get the following message: *** - CFFI requires CLISP compiled with dynamic FFI support. The problem seems to be that ffcall is not installed. When I try to install it with MacPorts, I get this message: $ sudo port install ffcall ---> Fetching ffcall ---> Attempting to fetch ffcall-1.10.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ffcall ---> Verifying checksum(s) for ffcall ---> Extracting ffcall ---> Configuring ffcall ---> Building ffcall Error: Target org.macports.build returned: shell command failed (see log for details) Log for ffcall is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ffcall/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> Here are my specs: - cl-mechanize 0.0 (depends on drakma) - drakma 1.2.3 (depends on cl+ssl) - cl+ssl 2007 - Quicklisp 2010121400 (used to install common lisp packages) - CLISP 2.49 - ffcall 1.10 - MacPorts 1.9.2 - Mac OS X 10.6.6 - MacBook Pro 5,1 Thanks for your consideration, Andrew Pennebaker http://www.yellosoft.us/

2 1