Re: [clisp-list] error in my nightly build from cvs

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...> [2008-10-12 12:32:28 -0700]:
>
> Sam Steingold writes:
>  > > * Don Cohen <qba...@vf...> [2008-10-11 21:30:00 -0700]:
>  > >
>  > > I don't see any such thing as dbus.
>  > >  [2008-10-11 21:17:57 root@don-eve ~] 
>  > >  $ find /tmp/clisp/ -name dbus 
>  > >  [2008-10-11 21:19:30 root@don-eve ~] 
>  > 
>  > http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/modules/dbus/
> Does this mean that 
>  cvs update
> from the clisp directory is not adequate?

it should be.

> Am I supposed to do another checkout?
> Where should I be in order to do what checkout?

dunno.
sorry.

>   Configure findings: 
>     FFI:        no (user requested: default) 
>
> Is this what you wanted?
> I'd have expected and preferred the opposite.

yes.
the default is to enable ffi if libffcall is found and to disable it
otherwise.
if you want configure to fail if libffcall is not found, use
--with-ffcall, if you do not want ffi even if libffcall is present, use
--with-ffcall=no or --without-ffcall.

this should be pretty clear from "configure --help".

>   # The default stack size on your platform is insufficient 
>   # and must be increased to at least 16384.  You must do either 
>   # 'ulimit -s 16384' (for Bourne shell derivatives, e.g., bash and zsh)
>
> That message is also unfamiliar to me.
> $ ulimit -s 
> 10240 

so do "ulimit -s 16384" before proceeding, as explained above.

> So I guess I'm now back on track.

looks like that!

> Is there some way to find out what options were passed to the original
> configure command?

not directly, however "clisp --version" prints plenty of information.

> Was I supposed to have used --disable-maintainer-mode in the original
> configure or do you think I did something wrong in some subsequent
> configure (unlikely, since this nightly build was working before), or
> was there some change in cvs (seems more likely) that made this
> necessary?

--disable-maintainer-mode merely removes Makefile targets which
regenerate configure scripts. they cannot affect the way clisp runs.
normally --disable-maintainer-mode is in force unless CVS directories
are present, indicating that a maintainer or an advanced user own the
source tree.

> If I were to do a new checkout of clisp, what would be the correct
> configure arguments?  I'd hope that ./configure build-dir would
> normally be the right thing, and would result in readline, FFI and
> libsigsegv all being "yes", at least if the required libraries exist.

if you have libffcall, libreadline et al installed in standard
locations, that is indeed the case.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 8.04 (hardy)
http://thereligionofpeace.com http://dhimmi.com http://openvotingconsortium.org
http://ffii.org http://honestreporting.com http://iris.org.il
Good programmers treat Microsoft products as damage and route around it.