summaryrefslogtreecommitdiff
path: root/meta/recipes-support/db
AgeCommit message (Collapse)AuthorFiles
2017-01-11db: disable the ARM assembler mutex codeLi Zhou1
The swpb in macro MUTEX_SET will cause "undefined instruction" error on the new arm arches which don't support this assembly instruction any more. If use ldrex/strex to replace swpb, the old arm arches don't support them. So to avoid this issue, just disable the ARM assembler mutex code, and use the default pthreads mutex. (From OE-Core rev: aafbc548ebc66dc0d703526f9a98f784e9c9605b) Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2016-09-30db: Refresh patchesRichard Purdie4
The patches were failing to apply in some cases, refresh them aganst the current source. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-29db: Upgrade to 6.0.35Aníbal Limón1
The SRC_URI was changed to point gentoo distfiles because now Oracle request authorization for download the source code [1], there are no changes in the LICENSE since version 6.0.20 when the LICENSE changes to AGPL-3 [2], also the md5sum was review to be sure that is the same. This minor upgrade fix an issue related to multiple rpm instances querying the database [3]. The bugfixes related are, - Fixed a bug that may lead to a crash when opening multiple environments in a multi-threaded program. - Fixed a bug where closing a panic environment raised access violation and crashed the program. For see the complete list of changes mostly bugfixes between 6.0.30 and 6.0.35 [4]. [1] http://download.oracle.com/otn/berkeley-db/db-6.0.35.tar.gz [2] http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_6_0.html#idp509784 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10157#c0 [4] http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_6_0.html#idp503384 [YOCTO #10157] Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-07-20db: Use cross libtoolKhem Raj2
Reintroduce the use of cross-libtool when building the target package this fails otherwise with clang | ./libtool --mode=execute true db_printlog | /usr/lib/libstdc++.so: file not recognized: File format not recognized | clang-3.9: error: linker command failed with exit code 1 (use -v to see invocation) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-07-10db: use S/B more idiomaticallyRoss Burton4
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. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-06-06db: add RECIPE_NO_UPDATE_REASONMaxin B. John1
db-6.2.23 does not work with RPM-5.x due to changes in locking semantics Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-09db: remove the NO_UPDATE_REASON and replace it a comment about RPMMark Hatle1
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2016-02-11db: update HOMEPAGEAndre McCurdy2
The previous HOMEPAGE is no longer available. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-02db: Use cross libtoolKhem Raj2
db is not reconfigured like usual autotools based components so it generates its own libtool, and this libtool is not equipped to do cross builds, e.g. when building using clang on musl, it misdirects linker to use libstdc++.so from build host instead of target, the reason being it does not understand sysroot. Use cross libtool instead to build the target versions Fixes errors like below | libtool: link: arm-oe-linux-musleabi-ranlib .libs/libdb-6.0.a | /a/builder/mnt/build-oe/tmp-musl/sysroots/x86_64-linux/usr/bin/arm-oe-linux-musleabi/arm-oe-linux-musleabi-ld: error: /usr/lib/libstdc++.so: incompatible target (From OE-Core rev: d14b5e650e1e55e30abbd884a6bbd9b4feacd923) 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>
2015-12-08package_regex.inc: split entries which blacklist specific versions to their ↵Alexander Kanavin1
recipes Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-12-01db: fix race issue for libdb-6.0.laRobert Yang2
Fixed: libtool: link: `os_map.lo' is not a valid libtool object Makefile:867: recipe for target 'libdb-6.0.la' failed Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-08-31upstream_tracking.inc: deprecate and move contents to recipesAlexander Kanavin1
No-update reasons and manual version checks should be in the recipes themselves because otherwise they're prone to getting out of date. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-04-02db: fix parallel issueRobert Yang2
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 Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-29db_6.0.30: modify SPDX_S variableleimaohui1
Modify SPDX_S to the source tree of db-6.0.30 instead of ${S}. Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
2014-09-29db_5.3.28: modify SPDX_S variableleimaohui1
Because $S is set to sub-directory of db-5.3.28. So modify SPDX_S to the source tree of db-5.3.28 instead of ${S}. Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
2014-07-08db: Add version 6.0.30Mark Hatle2
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-07-08db_5.3.*: Upgrade to 5.3.28Mark Hatle1
Simple upgrade, the license checksum change is related to a copyright date change. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-30db: Fix libtool linking against local libstdc++.soTyler Hall1
Building the C++ bindings in a484b35b818768487ff27cf06b8c5d4e128126af introduced this error on systems with /usr/lib/libstdc++.so present: /usr/lib/libstdc++.so: file not recognized: File format not recognized The shipped libtool is sysroot aware, so pass --with-sysroot so it will extract the sysroot from the compiler. Signed-off-by: Tyler Hall <tylerwhall@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-06db : Include C++ binding library in Berkeley DB recipe.Philip Balister1
Create the C++ library for db. This library is packaged in a new package so the db package only contains the c library. This prevents existing users from adding libstdc++ to the package DEPENDS. Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Douglas Geiger <doug.geiger@bioradiation.net> Signed-off-by: Steve Arnold <esteve@gentoogeek.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton1
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-11-04db: Fix build with high PARALLEL_MAKEMartin Jansa2
* sometimes it fails with: libtool: link: `util_log.lo' is not a valid libtool object make: *** [db_replicate] Error 1 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-10-30recipes: Remove PR = r0 from all recipesRichard Purdie1
Remove all PR = "r0" from all .bb files in oe-core. This was done with the command sed -e '/^PR.*=.*r0\"/d' recipes*/*/*.bb -i We've switching to the PR server, PR bumps are no longer needed and this saves people either accidentally bumping them or forgetting to remove the lines (r0 is the default anyway). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-16db: upgrade to 5.3.21Cristian Iorga1
License file changed the year, triggering a change in checksum Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-11-24db: update gnu-config files in do_configure()Marcin Juszkiewicz1
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-08-06python: Fix to support the python module _bsddb built with db 5.3Jackie Huang1
_bsddb module in python 2.7 could be built only with db version between 4.1 and 4.7. A patch was added to avoid build warning about this for [YOCTO #1937] but not actually fixed it. This patch enable _bsddb module be built with db 5.3, and remove --disable-statistics from the DB5_CONFIG to fix segmentation fault when using _bsddb module in python. [YOCTO #2749] Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-04db: use lib_package bbclassSaul Wold1
This is a clean-up following the recent addition of PN-bin to bitbake.conf and lib_package Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-06-19db: Ensure the library version matches package versionSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-06-18recipes: replace CONFLICTS with RCONFLICTS_${PN}Martin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-12rpm: Upgrade RPM to 5.4.8 (db to 5.3.15)Mark Hatle1
RPM 5.4.8 requires db 5.3.x, so both are upgraded together. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-19db: refactor packages for staticdevSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-07-05db: Add INSANE_SKIP to avoid warning about .so fileRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-23db: Fix file ownershipMark Hatle1
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-06-23db: Avoid stripping binariesMark Hatle1
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-05-27License Field Cleanup: Non-standard field namesBeth Flanagan1
I've cleaned up some odd license fields, fixed some license names and corrected some incorrect licenses. LICENSE really needs a pass through by the maintainers as some of the licensing is incorrect. Also, every license with Artistic should be gone through and noted as which version of Artistic. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
2011-05-12recipes: add Upstream-Status for multiple recipesDongxiao Xu1
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 Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-04-04db: Switch to patchdir rather than applying in do_configureTom Rini1
Signed-off-by: Tom Rini <tom_rini@mentor.com>
2011-03-18db: Fix path of arm-thumb patchMark Hatle2
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-01-27BerkleyDB: Uprev db from 4.2 to 5.1.19Mark Hatle5
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>
2010-12-23db: add LIC_FILES_CHKSUMSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-12-09SRC_URI Checksums AdditionalsSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-11-02openssl/db/gdbm: Extend to provide BBCLASSEXTEND nativesdkRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-01packages: Separate out most of the remaining packages into recipesRichard Purdie4
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 04:09:35 +0000