Re: loop-aes into busybox

* Alon Bar-Lev <[email protected]> wrote:

> I would expect something like --with-static-mount
> --with-static-losetup or something similar as parameters to
> configure.

Hm. It would be a nice feature, given that a patch with loop-AES
support exists for util-linux-ng. However, it would be even better if
Adrian Bunk had accepted the help offered so we hadn't to deal with
this fork mess in the first place :-(


> cal_test-cal.o:(.data+0x0): first defined here
> collect2: ld returned 1 exit status
> make[2]: *** [cal_test] Error 1
> 
> Tried to solve them one by one but gave up... :(

Same error pops up here (Slackwar 12, also gcc 4.1.2) 

<thinks>

Blaming it all on gcc stuff (which is way too often true these days)
a gcc 3.4 install comes up with this amusing message

CC=gcc34 CXX=g++34  LDFLAGS="-s -static" ./configure

checking for gcc... gcc34
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See `config.log' for more details.

Karel, any interest in that logfile? If so, have a look at
http://mareichelt.de/tmp/config.log

-- 
left blank, right bald
loop-AES FAQ: http://mareichelt.de/pub/texts.loop-aes.php

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG/sBNLMyTO8Kj/uQRAhVDAJ9eV3EgfvVsjsQWBgjZeNARMTNstwCfWtPB
eGT6G4PgmJMdLGzmcHlPgtk=
=HszQ
-----END PGP SIGNATURE-----