John, All, On Friday 12 August 2011 17:34:49 John Spencer wrote: > when compiling without this option, the crucial files ctri.o and crtn.o > don't get built. [--SNIP--] > overall this looks like a pretty useless and confusing option, which > imho should get removed. > even if there's a way to build a binary without those 2 object files, > which i'm not aware of (please point it out if you know how), it doesn't > cost nothing except of 1200 bytes harddisk storage to still build them.
I just looked on PPC-32, uClibc-0.9.30.2. The total size of code is 128 bytes, plus one long; which is a grand total of 132 bytes (if my maths are not too busted, and I did not miss any symbol). Also, looking at [0] (glibc-centric, but seems appropriate for uClibc as well), it seems that those two files are indeed really necessary. So, two questions: - is it at all possible to generate a proper uClibc-based toolchain without those two files? - even so, are those 132 bytes really worth an option in the menuconfig? [0] http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=2#doc_chap3 Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
