[Ecls-list] Integrating Monolithic Static Libraries with asdf

Seth Burleigh seth at tewebs.com
Sat Mar 27 19:47:31 UTC 2010


If i do that, i get: "Unknown initialization option :TYPE for class
#<The STANDARD-CLASS ASDF:PREBUILT-SYSTEM>"

asd file:

;;; Prebuilt ASDF definition for system utils;;; Built for ECL 10.3.1 on
a Linux/i686 2.6.31-20-generic
(ASDF:DEFSYSTEM :|utils|
                :CLASS
                ASDF:PREBUILT-SYSTEM
                :COMPONENTS
                ((:COMPILED-FILE "utils-mono"))

:type "fasb"
                :LIB
                #P"libutils-mono.a")

On Sat, 2010-03-27 at 20:40 +0100, Juan Jose Garcia-Ripoll wrote:
> On Sat, Mar 27, 2010 at 8:34 PM, Seth Burleigh <seth at tewebs.com>
> wrote:
>         It now all works except for this:  when i do
>          (asdf:make-build :utils :type :binary :monolithic
>         t :move-here
>         "~/lisp/")
>         
>         it no longer creates a .fas file, only a .a, .asd, and .fasb
>         file. If i
>         rename the .fasb file to .fas, it works, otherwise it fails
>         with
>         
>         "Filesystem error with pathname #P
>         \"/home/seth/lisp/utils-mono.fas\".
> 
> 
> This is a problem of recent ASDF which imposes its own choice of file
> extensions instead of trying all the possibilities from LOAD. Renaming
> is not a solution -- I had not contemplated the possibility of
> monolithic prebuilt systems, which must have the *.fasb extensions,
> but a simple workaround is to explicitely add the keyword :type "fasb"
> to the system definition. 
> 
> 
> Juanjo
> 
> -- 
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain) 
> http://tream.dreamhosters.com






More information about the ecl-devel mailing list