On 09/21/2016 12:48 PM, Felix Fietkau wrote: > On 2016-09-21 20:13, Florian Fainelli wrote: >> This patch series adds support for generating valid ld.so.cache which match >> the >> target architecture, without requiring a cross-compiled version of ldconfig >> that would run on the host, nor run on the target. >> >> Having a proper ld.so.cache might be needed if e.g: 64-bit executable loader >> only has /lib64 in its default search path. > Can't we simply fix the default search path instead? > Or is this a workaround for dealing with external toolchain braindamage?
Actually, we don't need to necessarily, the toolchain I use has all the essential C library under sys-root/lib64 (makes sense), however, when we do copy the external toolchain files in package/libs/toolchain/Makefile, we use dirname against the library file to determine the base folder. Considering that OpenWrt treats /lib and /lib64 the same way, or rather, forces everything to go under /lib, how about we just stop using dirname for the external toolchain libraries and just hardcode the library path to be /lib. Would that be more acceptable? Then we don't really need ldconfig at all. -- Florian _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
