When built aqgainst uclibc, busybox sed 's,^\#define[[:space:]]\{1\,\}BOOT_TRAMPOLINE[[:space:]]\{1\,\},,p' fails with "Invalid content of \{\}" message. When the very same tree is build against glibc, it works. On the library call level, it boils down to this call (the string has \ -> \\ escaped again by me, compiler will strip them back to single \): regcomp(®ex, "^\\#define[[:space:]]\\{1\\,\\}BOOT_TRAMPOLINE[[:space:]]\\{1\\,\\}", 0); which fails; regerror() reports "Invalid content of \{\}".
Created attachment 3968 [details] uclibc .config file The most relevant part is probably: UCLIBC_HAS_REGEX=y UCLIBC_HAS_REGEX_OLD=y
The uclibc source I used was uclibc-0.9.31.svn20110206
not sure how much effort is going to be spent here ... config UCLIBC_HAS_REGEX_OLD ... ... It also has some known issues when dealing with uncommon corner cases and multibyte/unicode strings. ... ... If the older version has worked for you ..., then stick with the old version (and say Y here). Otherwise, you should use the new version (and say N here). ...
(In reply to comment #3) > not sure how much effort is going to be spent here ... > > config UCLIBC_HAS_REGEX_OLD > ... > ... It also has some known issues when dealing with uncommon > corner cases and multibyte/unicode strings. ... > ... > If the older version has worked for you ..., > then stick with the old version (and say Y here). > Otherwise, you should use the new version (and say N here). > ... We should stop multiplying implementations of subsystems. We have two regexes, two FNMATCHs, two or three pthreads, two malloc's... What I forgot? Ah. We also have OLD_VFPRINTF. This is turning into a nightmare.
this is what happens when you have small implementations that mostly work, and then "full" implementations that contain stuff that most people don't care about patches welcome to improve this