Re: distributing clisp built with dynamic modules

[Jack U. <jd...@gm...>]

On Nov 5, 2007 3:17 PM, Sam Steingold <sd...@gn...> wrote:
>
> how about switching to --with-dynamic-modules being the default?
> the installation would then contain one (1) linking set - "boot"
> (installed as "base" for backwards compatibility) and dynamically
> compiled modules.

Sounds fine with me.

This is the first time that I've tried building --with-dynamic-modules
and I seem to be missing something called 'create-shared-lib'

CLISP_LINKKIT=. clisp-link add-module-sets boot base i18n syscalls
regexp || (rm -rf base ; exit 1)
make[1]: Entering directory
`/d/projects/third_party/working-dirs/clisp/build/i18n'
make[1]: Nothing to be done for `clisp-module'.
make[1]: Leaving directory
'/d/projects/third_party/working-dirs/clisp/build/i18n'
create-shared-lib -o
/d/projects/third_party/working-dirs/clisp/build/dynmod/lib -i18n.dll
gettext.o
./clisp-link: line 90: create-shared-lib: command not found
./clisp-link: failed in /d/projects/third_party/working-dirs/clisp/build/base
make: *** [base] Error 1

-- 
Jack Unrue