Hello, On Wed, 1 Mar 2017 21:30:31 +0000, Alexey Brodkin wrote:
> Speaking of "defconfigs" I really meant something that we may use > for building our toolchain outside of Buildroot if we want something that > differs from uClibc's defaults/defconfig - and most probably we'll need > something > either to add to uClibc's minimal_defconfig or exclude from > _maximal_defconfig. > > Otherwise how may we be in control of libc in our "reference" toolchain? A defconfig is what it is: a configuration provided as an example. Nothing forces you to use it. It's just an example. Buildroot doesn't use any of the uClibc-ng defconfigs. Buildroot has its own configuration for uClibc. You could just do the same for your reference toolchain. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com _______________________________________________ devel mailing list devel@uclibc-ng.org https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel
