Re: How to build statically-linked rekall?

> > How can I build statically-linked version of rekall, so that
> > it won't depend on shared libraries like libc etc.? It seems
> > that '--enable-static' option to 'configure' is not enough -
> > rekall still complains about missing shared libraries.
>
>
> This is going to be just about impossible. Internally rekall loads stuff 
> dynamically (drivers and parts like forms, reports, ....), so you'd have to 
> modify the code pretty heavily to link everything into one lump.


Is there is something that can be done, then, so that rekall
won't crash (i included backtrace data in my other post to the thread)?

Daniel.