> How does it affect the size of the libc binaries? It seems to be about 4k (the most concrete measurement I have is from compiling it standalone for x86_64; in OpenWrt builds it is hard to tell the difference, a few of the binaries are bigger by about 4k altogether).
I tested the difference in size in the OpenWrt images for brcm2708/armv6/raspi build and there is no trunk snapshot for it, so the size difference may also be due to the activity between AArc1 and current trunk. <side-note> I am using this setup for having a linux/unix user-space on my storage-limited android (non-rooted) device, in a proot (which is like a fakechroot but more "versatile"). The biggest advantage here is having a package manager etc. and not having to build my own mini-distro. The reason enabling standalone dynamic linker invocation (basically, this means being able to run the dynamic linker as an executable, I think) would be useful is because this can enable easy "OpenWrt/mini-linux-distro on android" (even without root): Download a static busybox from http://busybox.net/downloads/binaries/latest/ , compile proot http://proot.me/#downloads static-linked (it would be awesome to be able to download binaries of it too for many platforms), then download a openwrt-<something>rootfs.tar.gz and extract it using the static busybox. Then run proot using the rootfs-exctract-dir as file-tree-root, then run ". /etc/profile", make a resolv.conf if you want to use internet/dns, and you're done! This does not work flawlessly, but it is a very nice tool. </side-note> Anyway, thanks for the great work, openwrt devs! _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
