summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/db/db
Commit message (Collapse)AuthorAgeFilesLines
* db: Fix timespec length assumptionsKhem Raj2020-02-151-0/+45
| | | | | | | | | | | | This should fix the vdso crashes seen with kernel 5.0+ python3[11312] general protection fault ip:b7e966b0 sp:bf8175cc error:0 in libc.so[b7e8b000+6b000] (From OE-Core rev: a85afec1115f2a09cd750a4554f44fb8af96975c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db5: Fix build issues found with clang/libc++Khem Raj2019-01-211-0/+147
| | | | | | | | | This is a genuine error that is discovered when using libc++ runtime (From OE-Core rev: e4aa17ddc2ea623de2803efa9ab2fca498c99e19) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: drop legacy ARM specific SWP based mutex optimisationAndre McCurdy2018-06-281-50/+0
| | | | | | | | | | | | | | | | | | | | | | Although the ARM SWP instruction may exist for ARMv6 and above, it's not guaranteed to work, especially on SMP systems where it's use may lead to instability at runtime, etc: https://community.arm.com/processors/b/blog/posts/locks-swps-and-two-smoking-barriers Keeping the optimisation for architecture levels which pre-date SMP (ie <= ARMv5) may be safe, however other distros (Buildroot, Debian, Fedora, etc) are not doing so and mutex contention is likely to be less of an issue on uniprocessor systems anyway, so the benefits of this micro optimisations are not clear. Since OE uses ARMv5 qemu as a proxy for testing all 32bit ARM architecture levels, it's desirable to keep the ARMv5 builds aligned with later ARM architecture levels wherever possible. (From OE-Core rev: 7aa94abac09be6beb7ce14a2b9a409e934465706) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: change types to avoid headers changing between architecturesRoss Burton2017-11-081-0/+59
| | | | | | | | | | | | | | | | | | | | Triggered by looking at why Python doesn't find db.h (because it greps db.h for a regex, and db.h is actually a oe_multilib_header wrapper) I realised that the only reason we have to oe_multilib_header db.h is because one typedef is different between 32-bit and 64-bit architectures. However, the typedef is for a 64-bit integer so instead of using long (64-bit) or long long (32-bit), just use int64_t. Some of the overly complicated configure tests need to be deleted after this change but that is safe as we're building in a controlled environment and can assume int64_t exists. With this done the header doesn't change between architectures, and it doesn't need to be wrapped by oe_multilib_header. (From OE-Core rev: 60aa20b8b691e5a72a6a11bf795b86c6359db886) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Add --tag parameter to libtool invocationKhem Raj2017-08-251-0/+42
| | | | | | | | | | | | | | | | | | | Fix do_configure to be able to regenerate configure files Use cross libtool as installed by OE, as done in normal autotooled recipes These changes help in invoking the libtool with proper tags for C and C++ compiler and linker invocation and not use same tag across all different invocations Fixes errors like libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' (From OE-Core rev: afa9f769d62034d4443dfe929422d1d591adf709) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Fix atomic function namespace clash with clang builtinsKhem Raj2017-03-241-0/+45
| | | | | | | | | | Rename local function to avoid conflicts with compiler intrinsics (From OE-Core rev: fcfbbae9fdda539665a1e8bfe292f917bd5a1927) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: remove the 6.x recipeAlexander Kanavin2017-03-142-59/+0
| | | | | | | | | | | | | | | Version 6.x of Berkeley DB has been rejected by open source community due to its hostile AGPLv3 license; both Fedora and Debian are sticking with db 5.x - and by extension, all the open source projects are still developed and tested with db 5.x In oe-core the only thing that was requiring db 6.x was rpm 5.x, and so there's no reason to continue carrying db 6.x in oe-core. If someone needs API features that are only available in db 6.x, it can be re-added to meta-oe. (From OE-Core rev: 2694de76542840f79e3953c546d07b8ae479b8a1) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Refresh patchesRichard Purdie2016-09-304-18/+19
| | | | | | | | | The patches were failing to apply in some cases, refresh them aganst the current source. (From OE-Core rev: eb11f60d9d87aa24e93a86f366764b1848bb5cb1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: use S/B more idiomaticallyRoss Burton2016-07-102-4/+4
| | | | | | | | | | | | | | | | Instead of setting S to a directory inside the tarball and B to another directory inside the tarball, use the default value of S and set AUTOTOOLS_SCRIPT_PATH to the right path to find configure. Update the patches so they still apply, and clean up the recipe slightly. Because something is not quite right regarding quilt and patching, add a PR bump to the recipes to ensure that a clean work directory is used: for some reason rebuilds will rarely fail to patch correctly. (From OE-Core rev: dcbef72b8344c22617d65ea1e9f0fa7ad9a742bd) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: fix race issue for libdb-6.0.laRobert Yang2015-12-011-0/+32
| | | | | | | | | | | Fixed: libtool: link: `os_map.lo' is not a valid libtool object Makefile:867: recipe for target 'libdb-6.0.la' failed (From OE-Core rev: 5e0f27bd0d00dd9aa597d98d0a7d5b4f5d726925) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: fix parallel issueRobert Yang2015-04-021-0/+30
| | | | | | | | | | | | Fixed parallel issue: libtool: link: `bt_rec.lo' is not a valid libtool object Makefile:867: recipe for target 'libdb-6.0.la' failed make: *** [libdb-6.0.la] Error 1 (From OE-Core rev: b125feb069fd199c657df804453bd70e0e1939e2) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Add version 6.0.30Mark Hatle2014-07-081-0/+10
| | | | | | | | | | | | The latest version of RPM5 requires Berkley DB 6.0.20 or newer. The license is now AGPL-3.0 in BDB 6.0. This may not be acceptable to some, so the previous version is retained as an alternative. (From OE-Core rev: 04bb223110da2f92725c341bc3ec0cf26325f675) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Fix build with high PARALLEL_MAKEMartin Jansa2013-11-051-0/+19
| | | | | | | | | | | | * sometimes it fails with: libtool: link: `util_log.lo' is not a valid libtool object make: *** [db_replicate] Error 1 (From OE-Core rev: 0a1efeb6260a565b6ce3abd523eabb15384570d1) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: add Upstream-Status for multiple recipesDongxiao Xu2011-05-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hostap: add upstream status for hostap-fw-load.patch lrzsz: add upstream status for lrzsz's patches bluez: add upstream status for bluez's patches bluez-dtl1-workaround: add upstream status for COPYING.patch libgsmd: add upstream status for gsm's patches. gypsy: add upstream status for gypsy's patch libpcap: add upstream status for libpcap's patches ppp: add upstream status for ppp's patches libtelepathy: add upstream status for libtelepathy's patches telepathy-python: add upstream status for telepahty-python's patches wireless-tools: add upstream status for wireless-tools's patches wpa-supplicant: add upstream status for wpa-supplicant zeroconf: add upstream status for zeroconf's patch glibc: add upstream status for glibc's patches dpkg: add upstream status for dpkg's patches makedevs: add upstream status for makedevs's patch opkg: add upstream status for opkg's patches opkg-utils: add upstream status for opkg-utils's patch minicom: add upstream status for minicom patches rpcbind: add upstream status for rpcbind's patch which: add upstream status for which's patch clutter-gst: add upstream status for clutter-gst's patches flac: add upstream status for flac's patches gst-ffmpeg: add upstream status for gst-ffmpeg's patch liba52: add upstream status for liba52's patch libid3tag: add upstream status for libid3tag libmusicbrainz: add upstream status for libmusicbrainz's patch pulseaudio: add upstream status for pulseaudio patches db: add upstream status for db's patch neon: add upstream status for neon's patch taglib: add upstream status for taglib's patches libetpan: add upstream status for libetpan's patch libopensync: add upstream status for libopensync's patches libopensync-plugin-evolution2: add upstream status for its patch libopensync-plugin-syncml: add upstream status for its patch libsyncml: add upstream status for libsyncml's patch empathy: add upstream status for empathy's patch wv: add upstream status for wv's patch xournal: add upstream status for xournal's patch (From OE-Core rev: 0f9f0518ac46c2f2beb0224e881ff136f1603d33) Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Fix path of arm-thumb patchMark Hatle2011-03-181-2/+2
| | | | | | | | | | | | | | Newer versions of patch, such as in Fedora 14, don't like ".." within the middle of the file to be patched path. In order to fix the issue we have to hand apply the patch instead of using the normal mechanisms. Only flaw with the os.system(...) approach is if it fails we don't get any notification or a resolver failure. (From OE-Core rev: 4e592efe8c5ff918a77f7b7b2c17a6b698b1dd68) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* BerkleyDB: Uprev db from 4.2 to 5.1.19Mark Hatle2011-01-273-54/+36
| | | | | | | The latest version of Berkley DB (5.1.19) is required by RPM. This version is backwards compatible with the 4.2 version that was enabled previously. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* packages: Separate out most of the remaining packages into recipesRichard Purdie2010-09-012-0/+54
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>