As an alternate to statically linking it, you can put the appropriate
librarys in the chrooted sandbox. Arguably not as secure, but it does
work. It depends on why you want the chroot, I guess.
You can use ldd to tell you which libraries are needed by a given
executable:
% ldd rrdtool
libm.so.6 => /lib/libm.so.6 (0x4001b000)
libc.so.6 => /lib/libc.so.6 (0x40038000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
...for example...
To answer the question you actually asked, I don't know how.. I've
never bothered to think about it. :)
-Mark
Venko Moyankov wrote:
> hi,
>
> How can I make static linked rrdtool binary. I tryed with:
> $ ./configure --enable-static
> $ make
> but the binary is dinamically linked:
> $ file ./src/.libs/rrdtool
> ./src/.libs/rrdtool: ELF 32-bit LSB executable, Intel 80386, version 1,
> dynamically linked (uses shared libs), not stripped
>
> Is there any way to convert it to static linked? I need static link
> version to start it with chroot.
>
> Thanks,
> Venko Moyankov
>
> --
> Unsubscribe mailto:[EMAIL PROTECTED]
> Help mailto:[EMAIL PROTECTED]
> Archive http://www.ee.ethz.ch/~slist/rrd-users
> WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
--
Unsubscribe mailto:[EMAIL PROTECTED]
Help mailto:[EMAIL PROTECTED]
Archive http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
