openssh static build - mission impossible?

Nico Kadel-Garcia nkadel at gmail.com
Wed Mar 7 12:29:10 EST 2012


On Tue, Mar 6, 2012 at 1:51 PM, Peter Stuge <peter at stuge.se> wrote:

> Ángel González wrote:
> > Recompiling the same glibc version, but from upstream[1] instead of
> > Fedora should theoretically work. Although I agree replacing glibc is
> > not without risks.
>
> I think libc can be left alone, all that is needed is a crypt()
> implementation. If DES_crypt() can be used as-is then the missing
> piece of the puzzle is a trivial wrapper.
>

It does seem to be turning into a seroius project. Building from SRPM spec
files, cross-compiling, and trying to do a static build seems like a very
long chain of links of chain to shove through a slot: one link might pass,
but passing two or three in a row seems like an akward attempt.

Is it possible to factor the problem? To compile on the same platform
you're aiming for, to avoid the cross-compiler issues or to compile cleanly
without the cross-compilaton? Is it possible to compile with bare source,
not using the SRPM structure? And is it possible  to build properly with
the shared libraries, just so that each factor can be scaled back one at a
time?


More information about the openssh-unix-dev mailing list