summaryrefslogtreecommitdiffstats
path: root/meta/classes/qt4x11.bbclass
diff options
context:
space:
mode:
authorMark Hatle <mark.hatle@windriver.com>2012-09-29 19:19:18 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-02 11:40:50 +0100
commiteab49954002c26bab4bffd344c1fd82d8f524f6e (patch)
tree5e6712221bb3917c0cdaf7a64a6c535b6df94d84 /meta/classes/qt4x11.bbclass
parente602247c0823f7076bf518f6c51a5ea76e529840 (diff)
downloadpoky-eab49954002c26bab4bffd344c1fd82d8f524f6e.tar.gz
rpm: Implement workaround for DB_BUFFER_SMALL error
In certain cases with BerkleyDB 5.3.x we are getting the error: db3.c:1443: dbcursor->pget(-30999): BDB0063 DB_BUFFER_SMALL: User memory too small fo See https://bugs.launchpad.net/rpm/+bug/934420 for more information. It appears to be some type of a bug in the BerkleyDB 5.3.x. In an attempt to workaround the problem, when we encounter this situation we attempt to adjust the size of the mmap buffer until the call works, or we end up trying 10 times. The new size is either the updated vp->size from the failed pget call, or the previous size + 1024. If DBI debugging is enabled, additional diagnostics are printed, otherwise a basic retry and success message is added to show that the failure was resolved. (From OE-Core rev: bfb2906206158748d0be33baf7984cf885756da1) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/qt4x11.bbclass')
0 files changed, 0 insertions, 0 deletions