gsll-devel September 2009

gsll-devel@common-lisp.net

1 participants
2 discussions

[Gsll-devel] clisp&cffi: broken foreign functions in saved images
by Sam Steingold 06 Jan '10

06 Jan '10

Hi, I do this: $ clisp -x '(asdf:operate 'asdf:load-op :gsll) (saveinitmem "gsll" :executable t)' $ ./gsll > > (gsll:make-chebyshev 1) FFI::FOREIGN-CALL-OUT: no dynamic object named "gsl_cheb_alloc" in library :DEFAULT this indicates a bug somewhere between cffi and gsll. specifically, the definition of the foreign function gsl_cheb_alloc should specify that it is to be found in "libgsl.so", not in :default. moreover, when I do the (not so) trivial thing: (ffi:default-foreign-language :stdc) (ffi:open-foreign-library "libgslcblas.so") (ffi:def-call-out gsl_cheb_alloc (:library "libgsl.so") (:arguments (n ffi:int)) (:return-type ffi:c-pointer)) (gsl_cheb_alloc 10) ;; ==> #<FOREIGN-ADDRESS #x0000000005503380> (saveinitmem "foo" :executable t) (quit) ./foo (ffi:open-foreign-library "libgslcblas.so") (gsl_cheb_alloc 10) #<FOREIGN-ADDRESS #x0000000001D9F4C0> i.e., if the foreign function definition includes the correct library name, the function will work automatically[*] even in the saved image. So, since I am not quite sure where the bug is hiding, I am reporting this to both gsll and cffi lists. Thanks. Sam. [*] apparently, libgsl.so cannot be loaded before libgslcblas.so is. how do people specify such dependencies?!

2 7

[Gsll-devel] gsll compilation with sbcl 1.0.30
by Simon Holgate 17 Sep '09

17 Sep '09

Hello, this is my first post to the list. I've tried the archives but not found an answer. Apologies if this has come up before. I've successfully installed gsll previously under SBCL, with a system-wide SBCL install, and everything worked just fine. On my current system I've had to install everything under my local user directory and SBCL (1.0.30) has been installed there too, compiled from source. I've installed all the dependencies but I get a problem on compilation. I've pasted all the output below. The issue seems to be with CFFI-GROVEL and I guess that it can't find libgsl. That is also installed locally under $HOME/lib and is exported in my LD_LIBRARY_PATH. Is there some other way to point to libgsl or have I got the wrong end of the stick? BTW when first compiling I also got an error (which isn't replicated below) about not being able to find "gsl_version" and something to do with a missing "ALIEN-..."? The host system is SUSE (SLED 10). Any help would be much appreciated. Thanks, Simon Output from SBCL was: * (require 'asdf) ("ASDF") * (asdf:operate 'asdf:load-op :gsll) ; loading system definition from /login/simonh/.sbcl/systems/gsll.asd into ; #<PACKAGE "ASDF0"> ; loading system definition from /login/simonh/.sbcl/systems/fsbv.asd into ; #<PACKAGE "ASDF1"> ; loading system definition from /login/simonh/.sbcl/systems/cffi-grovel.asd ; into #<PACKAGE "ASDF2"> ; registering #<SYSTEM CFFI-GROVEL {AD3DDD9}> as CFFI-GROVEL ; loading system definition from /login/simonh/.sbcl/systems/alexandria.asd ; into #<PACKAGE "ASDF2"> ; registering #<SYSTEM :ALEXANDRIA {B18FCA1}> as ALEXANDRIA ; loading system definition from /login/simonh/.sbcl/systems/cffi.asd into ; #<PACKAGE "ASDF2"> ; registering #<SYSTEM CFFI {B37BD09}> as CFFI ; loading system definition from /login/simonh/.sbcl/systems/babel.asd into ; #<PACKAGE "ASDF2"> ; registering #<SYSTEM BABEL {B4E9BA9}> as BABEL ; loading system definition from ; /login/simonh/.sbcl/systems/trivial-features.asd into #<PACKAGE "ASDF2"> ; registering #<SYSTEM TRIVIAL-FEATURES {AA30489}> as TRIVIAL-FEATURES ; registering #<SYSTEM :FSBV {AD0E019}> as FSBV ; registering #<SYSTEM "gsll" {AFA1949}> as gsll ; loading system definition from /login/simonh/.sbcl/systems/cl-utilities.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM CL-UTILITIES {B18FD31}> as CL-UTILITIES ; loading system definition from ; /login/simonh/.sbcl/systems/trivial-garbage.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM TRIVIAL-GARBAGE {A939841}> as TRIVIAL-GARBAGE ; registering #<SYSTEM TRIVIAL-GARBAGE-TESTS {AA79521}> as TRIVIAL-GARBAGE-TESTS debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread" RUNNING {A9007A9}>: The value NIL is not of type PACKAGE. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [TRY-RECOMPILING] Try recompiling libgsl 1: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {AFFFC71}> on #<CFFI-GROVEL:GROVEL-FILE "libgsl" {BAFB3D1}>. 2: [ACCEPT ] Continue, treating #<ASDF:COMPILE-OP NIL {AFFFC71}> on #<CFFI-GROVEL:GROVEL-FILE "libgsl" {BAFB3D1}> as having been successful. 3: [ABORT ] Exit debugger, returning to top level. ((LABELS CFFI-GROVEL::PROCESS-FORM) (IN-PACKAGE :GSL)) 0] 0 debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread" RUNNING {A9007A9}>: The value NIL is not of type PACKAGE. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [TRY-RECOMPILING] Try recompiling libgsl 1: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {AFFFC71}> on #<CFFI-GROVEL:GROVEL-FILE "libgsl" {BAFB3D1}>. 2: [ACCEPT ] Continue, treating #<ASDF:COMPILE-OP NIL {AFFFC71}> on #<CFFI-GROVEL:GROVEL-FILE "libgsl" {BAFB3D1}> as having been successful. 3: [ABORT ] Exit debugger, returning to top level. ((LABELS CFFI-GROVEL::PROCESS-FORM) (IN-PACKAGE :GSL)) 0] 3 ; ; compilation unit aborted ; caught 1 fatal ERROR condition * (quit) -- **x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x**x** Dr. Simon Holgate, Permanent Service for Mean Sea Level, Proudman Oceanographic Laboratory, Joseph Proudman Building, 6 Brownlow Street, Liverpool L3 5DA, England Tel: +44 (0) 151 795 4900 (direct), +44 (0) 151 795 4800 (switchboard) FAX: +44 (0) 151 795 4801 http://www.pol.ac.uk/home/staff/?user=HolgSimo == -- This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

gsll-devel September 2009