I am curious as I was not even aware that you could tell the compile process to use one uClib erosion or another. I thought that was fixed through the toolchain compile process. How do you get the buildroot process to use a certain uClib version then?
Kind Regards Hanno Schupp Connect Consulting Services Chillifire is a trademark owned by CCS On 16/04/2012, at 10:18 AM, Felix Fietkau <n...@openwrt.org> wrote: > On 2012-04-16 12:10 AM, Jim Henderson wrote: >> On Sun, 15 Apr 2012 23:59:15 +0200, Felix Fietkau wrote: >> >>> OpenWrt has been using uClibc 0.9.33 for a while now, whereas you seem >>> to be using 0.9.32. It looks like 0.9.33 provides that missing function. >> >> Awesome, thanks - seems the last time uClibc was updated I had a similar >> issue, and had forgotten about it. >> >> Will reconfigure to use the updated uClibc and let it build with that. > If you want to see what changes your .config has compared to the > default, just run ./scripts/diffconfig.sh - that's an easy way of > spotting such issues. > > - Felix > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
