On Wed, Jul 24, 2019 at 7:58 AM Adrian Bunk <[email protected]> wrote: > > On Wed, Jul 24, 2019 at 06:39:16AM -0700, Khem Raj wrote: > > On Wed, Jul 24, 2019 at 1:24 AM Richard Purdie < > > [email protected]> wrote: > > > > > On Sun, 2019-07-21 at 18:20 +0300, Adrian Bunk wrote: > > > > On Sat, Jul 20, 2019 at 11:00:57AM -0700, Khem Raj wrote: > > > > > ... > > > > > ++#if !defined(FNM_EXTMATCH) > > > > > ++# define FNM_EXTMATCH (0) > > > > > ++#endif > > > > > ... > > > > > > > > As already said in [1] this is expected to result in broken code, > > > > and the upstream testsuite also confirms this. > > > > > > I've taken the patches as they don't make things worse. I am a bit > > > concerned about a few places musl is building up problematic patches > > > though (systemd, elfutils, ltp come to mind). > > > > > > > Yes I am aware of this I think LTP we are upstreaming and I hope this will > > be better in future > > Systemd we might have to re-evaluate but I think few patches are worthy of > > upstreaming elfutils I don’t know yet > > elfutils and the same bogus change in ifupdown might need the > implementation from glibc added as an own package, similar to > what you've already done for argp and obstack. >
yes FNM_EXTMATCH change needs to be done logically at app level, instead of defining it sometimes apps just use it because its available and covers vast set that maybe otherwise not needed. > cu > Adrian > > -- > > "Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. > "Only a promise," Lao Er said. > Pearl S. Buck - Dragon Seed > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
