On Sun, Jun 26, 2011 at 07:42:23PM -0500, Rob Landley wrote: > > The 0.53 release of dropbear had -lcrypt symbols referenced in .o or .a > files _after_ libcrypt on the link command line. Thus they were > unresolved, and the link failed. > > I reported this here, and in response matt moved -lcrypt to the _start_ > of the command line, before _anything_ references it, thus making the > -lcrypt into a NOP for static linking. He then cut a 0.53.1 release > that _still_ didn't statically link, presumably without ever testing the > static linking fix.
Yes, that was a bit unfortunate. I've attached a patch that should hopefully fix all of it (against 0.53.1). The rationale for the original (broken) change was so that only the "dropbear" binary would link -lcrypt, others don't need it. > I use the attached patch to build a static dropbear 0.53.1 in Aboriginal > Linux. I have no idea if it's the _right_ fix because autoconf is an > abomination that dropbear didn't used to use, but which it got infected > by a few years ago for no obvious reason. Dropbear has used autoconf since the first public release in 2003*, mainly just for differences on non-Linux unixes. The build's a bit horrible, but that's all just GNU make. Rob's patch looks OK though anyway. Matt * http://cvs.ucc.asn.au/cgi-bin/viewvc.cgi/anoncvs/projects/dropbear/configure.in?revision=1.1&view=markup
