Jason A. Donenfeld wrote: >Oh interesting. I wonder what's different about your >config/compiler... I guess that means we can change the menuconfig >entry to say (1.8k) instead.
My understanding is that the applet sizes reported in config are to be generated by running the make_single_applets.sh and size_single_applets.sh scripts. Bloatcheck tells us the incremental cost of the patch versus a fully configured build whereas the scripts report the cost of creating a single-applet binary relative to the minimum possible single-applet binary. The latter cost will be (roughly) the size reported by bloatcheck plus any dependent code it pulls in beyond that required by the minimal applet. For current git on my system I get "seedrng (8.3 kb)". The comments in size_single_applets.sh say that a 32-bit build should be used: # CONFIG_STATIC is not set CONFIG_CROSS_COMPILER_PREFIX="" CONFIG_EXTRA_CFLAGS="-m32" CONFIG_EXTRA_LDFLAGS="-m32" However, this configuration failed to link due to problems with the recent hardware accelerated SHA1/SHA256 code. So I edited the config to include: # CONFIG_SHA1_HWACCEL is not set # CONFIG_SHA256_HWACCEL is not set Cheers, Ron _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
