Fiddling with menuconfig: DOPIC (Create only position independent code)
Does not say why you would or wouldn't want to do this. (Does it generate position independent code and non-position independent code? Should the .a files also be PIC, or just the .so files? If you select this are you telling it _not_ to generate any .a files, so static linking isn't an option? Is there a downside to statically linking PIC code?) FORCE_SHAREABLE_TEXT_SEGMENTS: Should this depend on DOPIC? I switched that off, but this was still there and still enabled. The help sort of implies it's no longer usable...? Or is it still generating a full PIC version and a full non-PIC verson? LDSO_LDD_SUPPORT The help should start by saying the uClibc version of ldd doesn't need this, unless that's changed. LDSO_PRELOAD_FILE_SUPPORT: A list of libraries to be loaded before "the program". Do you mean before each program? Or is there a way of specifying specific programs? LINUXTHREADS_OLD: Ok, what does this currently mean? This selects the old libpthreads implementation from the dawn of time, but what's the alternative? The new NPTL stuff hasn't been merged yet, so this intermediate version is... what? (And while we're at it, what does this mean: ./libpthread/linuxthreads.old/sysdeps/x86_64/pt-machine.h:39: warning: register used for two global register variables ) UCLIBC_HAS_STUBS This is just "fork on nommu", right? Shouldn't it be under nommu sypport and depend on it? UCLIBC_HAS_TZ_CACHING Wouldn't it be a good idea to move this _after_ UCLIBC_HAS_TZ_FILE and make it depend on that? Otherwise what are you caching, exactly? (The TZ environment variable? If so, the help needs updating.) UCLIBC_HAS_STRING_GENERIC_OPT UCLIBC_HAS_STRING_ARCH_OPT Um, am I supposed to pick one? Both are enabled by default, and both say they should be Y. Do both get used at the same time by the same arch? UCLIBC_HAS_STDIO_BUFSIZ UCLIBC_HAS_STDIO_BUILTIN_BUFFER What's the difference here? Neither of these has a help entry... UCLIBC_HAS_STDIO_SHUTDOWN_ON_ABORT This needs to be wordwrapped to fit in an 80x25 menuconfig instance. (Take a look, you have to scroll right to read it.) And it's "effect" of, not "affect" of. And I think the help text means that answering "N" will make abort async signal safe as required by C99 (and allowed by susv3), but it means abort may discard pending output. UCLIBC_HAS_STDIO_AUTO_RW_TRANSITION Again, wordwrap it to fit in the help window menuconfig is displaying on an 80x25 terminal, and whie you're at it what's with the high ascii characters in "end?of?file" at the end of the second paragraph? UCLIBC_BUILD_RELRO UCLIBC_BUILD_NOW There are no help entries for these, and no _clue_ why one defaults to on and the other off. Rob -- "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
