[Roman Zippel] > If your build environment doesn't support shared libraries, you can > easily generate a static library instead and link against it > yourself, like you described, but it's no reason to deny the > convenience to working environments.
Yeah, but until I do, I can't even run 'make oldconfig'. (This isn't about me - I will probably always build on Linux, with gcc - it's about weird environments like cross-compiling from Solaris, which I'm told was often done in the earlier stages of SPARC Linux.) I suggest that *at least* the built-in targets should link libkconfig statically - either via libkconfig.a or just the list of .o files. Peter ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
