tho...@koeller.dyndns.org wrote:
> Description:
> I failed at building a statically linked, working bash. First of all,
> the only way to build is
> by giving the '--with-bash-malloc=no' argument to configure, because
> otherwise the linker will
> complain about multiple definitions of 'malloc' and 'free', which of
> course are present in libc.
> Even so, the binary resulting from the build will crash during
> startup, inside the getpwuid()
> function. I found a mail thread that describes a similar problem for
> bash-3.2 on Solaris
> http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00011.html.
> Like the reporter, I configured
> my system to use LDAP for authentication. Only if I run bash as the
> root user, which is a local
> account outside the ldap directory, there is no crash and it appears
> to work.
It's the same problem. There are portions of the Linux C library that
cannot be used by a statically-linked program. The best you can do is
to link those portions dynamically and the remainder statically.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
