[buildd-tools-devel] Statically-linked Schroot

[Daniel Thau]

First of all, I would like to say that schroot is a wonderful piece of
software; my compliments to Roger Leigh and all of the other developers
who worked on it.  I've been regularly surprised how useful it can be.

I would like to compile schroot statically-linked, so that it does not
depend on the libraries installed on the system after the compilation
has finished.  My ultimate goal is to be able to simply bind mount
schroot's directory into just about any chroot, to allow that chroot to
use schroot irrelevant of the libraries installed in that chroot
(possibly with some symlink and/or $PATH work).

I realize that, should I manage to do this successfully, there are at
least two problems with it:

1. Schroot will end up being much larger than it would be if I did not
compile it statically-linked.  I am willing to live with the disk space
overhead.

2. There is a bit of a security concern, in that if a library is updated
I would have to recompile schroot against it for any security benefits
from the update to take place.  I am willing to live with this as well;
I will be diligent about watching for such updates.

I tried to figure out how to do this on my own before seeking help.
Searching Google, I've found nothing about statically-linked compiling
schroot specifically, but I learned that many programs could be compiled
statically-linked by either giving their configure script the proper
flags  or setting the LDFLAGS environmental variable to the proper
values in the proper places, and so I began guessing and checking with
various combinations of flags, environmental variable values, and
various versions of schroot.  I was unable to find a functional
solution; I would always get some sort of error or ldd would tell me it
the schroot executable is not statically linked.  I figured the next
logical step was to ask people who are likely to be both more
knowledgeable about the whole concept of statically-linked compilation
and schroot itself.

My questions are:

1. Are there any other possible problems with statically-linked
compiling schroot which I may have overlooked?

2. Irrelevant of such problems, how would I go about compiling schroot
statically-linked?

Thank you,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20111020/50b45b56/attachment.pgp>