summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* dhcp: package /var/lib/dhcp with dhcp-client rather than dhcp-serverSteve Sakoman2012-01-162-3/+3
| | | | | | | | | | | Otherwise dhclient encounters errors of this type: dhclient: can't create /var/lib/dhcp/dhclient-c0c60402-0bc5-4bd7-bc3b-49a27fa37d72-eth1.lease: No such file or directory (From OE-Core rev: aad04928116feea421fba84c4780b93191be6169) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cairo 1.10.2: enable tee backendKoen Kooi2012-01-162-2/+4
| | | | | | | | | | | | | This is needed for firefox: | checking CAIRO_LIBS... -lcairo -lpixman-1 -lfreetype -lfontconfig | checking for cairo-tee >= 1.10... Package cairo-tee was not found in the pkg-config search path. Perhaps you should add the directory containing `cairo-tee.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo-tee' found | configure: error: Library requirements (cairo-tee >= 1.10) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. (From OE-Core rev: 935ae84757ca623f93b1465088e27107bc226dee) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pango.inc: add directory "/etc/pango"Xiaofeng Yan2012-01-162-2/+6
| | | | | | | | | | | | | | Command "pango-querymodules > /etc/pango/pango.modules" can't work when \ starting up yocto because of no directory "/etc/pango". It will cause \ messy code when gtk-demo running. [YOCTO #1900] [RP: PR bump] (From OE-Core rev: 65186bd86170d8c375931a18487c2fdf3bd1b3b0) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cairo.inc: Change configuration of directfb to gtk-directfbXiaofeng Yan2012-01-161-1/+1
| | | | | | | | | | | | "direcdtfb" is a wrong configuration in PACKAGECONFIG. It should be "gtk-directfb". PACKAGECONFIG can't select directfb as backend rightly, or else. [YOCTO #1900] (From OE-Core rev: 458ffd3f47b99ee89e6cb8015d68f9820f86e3e7) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk.inc: Change configuration of directfb to gtk-directfbXiaofeng Yan2012-01-161-1/+1
| | | | | | | | | | | | "direcdtfb" is a wrong configuration in PACKAGECONFIG. It should be "gtk-directfb". PACKAGECONFIG can't select directfb as backend rightly, or else. [YOCTO #1900] (From OE-Core rev: 785412c0dfb8df055e3f5fa865474ee1cf0ce10f) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/knotty: print task failure summaryPaul Eggleton2012-01-152-6/+22
| | | | | | | | | | | | | | | | Remove the error logged within cooker summarising the list of failed tasks, and instead print this in the UI (knotty) where it belongs. This also adds the actual name of the task that failed as well as the corresponding recipe file that was being shown previously. In addition, reformat the summary messages more tidily - no extra breaks between lines and use correct English singular/plurals, with some allowance for future translation. (Bitbake rev: cdf69913f99d28bc7f51067a60257701f952c6cb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/cooker: avoid printing stack trace for -b match errorPaul Eggleton2012-01-151-6/+11
| | | | | | | | | | | | | | | | | | | | | Improves error output for matching problems when the -b / --buildfile command line option is used. Rename MultipleMatches exception to NoSpecificMatch (as it is also raised when there are no matching recipes) and make it inherit from BBHandledException so that it doesn't print a stack trace (we always log an ERROR prior to raising it.) In addition, improve the formatting of the error message - only call the log function once rather than once for every match, and use a more appropriate message if there are no matches. Fixes [YOCTO #1141] (Bitbake rev: 803550a5098ec878164245e71344c3d687310b72) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/fetch2: reduce output for fetch failuresPaul Eggleton2012-01-151-1/+6
| | | | | | | | | | | | | | | | | | | Make the warning for the initial fetch failure a single line - we don't need the full command and output here yet, but write it into the log in full as a debug message. However, if fetching from mirrors fails as well then print out the full details for the first error that occurred as an ERROR rather than a WARNING. Since this is logged as an ERROR, combined with an earlier patch it suppresses the full log which does make the output much more readable for any fetch error. Fixes [YOCTO #1832]. (Bitbake rev: 6bbdc7d259c0cc041b62dbdb26cfc3ec6edcb6f3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/knotty: avoid printing full task log when error already printedPaul Eggleton2012-01-152-4/+16
| | | | | | | | | | | | | | If a task has logged an ERROR then don't print the contents of the task's log file in knotty (the default terminal UI). As a side-effect we now also respect BBINCLUDELOGS in knotty; if it is false we never print the log (but the pointer to the log file is always printed). (Bitbake rev: b9746b7e4d7aa5c34eba15a61427bfc6949af123) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/fetch2: correctly decode exit signal/statusPaul Eggleton2012-01-151-4/+7
| | | | | | | | | | | | | The termination signal and exit code of the fetch process were not being decoded correctly, resulting in bitbake reporting that the process terminated with a signal of the exit code (if it was under 255). There are functions in the Python os module to do this decoding correctly (for Unix at least), so let's use them. (Bitbake rev: 50aea9a76e40cf71cc3f1462c88298e4846a031c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/runqueue: avoid "failed" in task summary if nothing didPaul Eggleton2012-01-151-1/+5
| | | | | | | | | | | | | | | | Seeing the word "failed" alone without reading the whole context has occasionally triggered an automatic assumption on the part of some users (myself included) that something has gone wrong, even when this message is telling you that "0 [tasks] failed". To avoid this let's just say "all succeeded" in this case instead. As a bonus this means you can now search the output for "fail" and not find anything if all went well. (Bitbake rev: b6f067af12d4661758a78788f1db472684b9aba8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/fetch2: improve error formatting for fetcher errorsPaul Eggleton2012-01-152-5/+8
| | | | | | | | | | | | | | | * The "name" argument to FuncFailed is rarely used as a name in actual usage within bitbake, so don't treat it as one in the output. * Don't print URL for FetchError if it was not specified (i.e. don't output "Fetcher failure for URL 'None'") * Don't include URL in "unable to fetch from any source" message since we supply it to FetchError and it will be printed anyway. * Don't include URL in "checksum failed" message for the same reason (Bitbake rev: 86811bd85e2e453ee92a05fe60160d9b49ac69e8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/knotty: don't count errors as warnings in summaryPaul Eggleton2012-01-151-1/+1
| | | | | | | | | | The count of warnings being shown in the summary at the end was also including the number of errors. (Bitbake rev: d242d6ca81dd83b2b13a3ac77ac4cd829a69cf83) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patch.bbclass: Ensure the DATE and SRCDATE variable exclusions apply to the ↵Richard Purdie2012-01-131-1/+3
| | | | | | | | | | | | | correct function People have noticed that sstate is now getting invalidated very readily. The issue is that the code using these variables was factored into a new function but the variable exclusion was not. This patch moves the variable exclusion to the correct place allowing the sstate checksums to work correctly. (From OE-Core rev: bd047935305c872b565f30b46c94b7077e5fb3a2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.conf: Clean up file and add missing entries for various dependencies1.2_M2.rc11.2_M2.final1.2_M2Richard Purdie2012-01-111-15/+22
| | | | | | | | | This patch adds in various missing dependencies to ensure the set of recipes listed for multilib support can be cleanly built. (From OE-Core rev: 1d2697e6f00cc3771f39f5a7d4384a22d9696b16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils-cross-canadian: Clear BBCLASSEXTEND as a native version of this ↵Richard Purdie2012-01-111-0/+2
| | | | | | | | recipe makes no sense (From OE-Core rev: 5980cd6af7b5260558cb234288a426c091b5de2a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-native: RPROVIDE python-core-native since pycurl-native depends on itRichard Purdie2012-01-111-1/+1
| | | | | | (From OE-Core rev: 893405d46c28d75372dcf4b2d91c617b81bdc92e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxft: Drop BBCLASSEXTEND nativesdk since dependencies freetype and ↵Richard Purdie2012-01-111-1/+1
| | | | | | | | fontconfig aren't class extended (From OE-Core rev: 27e8a432889b3a78f6bbadf8b14ad1ce4d11907c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lzo: Add BBCLASSEXTEND nativesdk so lzop nativesdk works (it depends on this)Richard Purdie2012-01-111-1/+1
| | | | | | (From OE-Core rev: 6dd84aa0bb766190e82d401511808715625e4310) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Fix magic file name magic -> magic.mgcSaul Wold2012-01-111-2/+2
| | | | | | | (From OE-Core rev: aee38df69073fe5b3c1e8ee180912d1f0360f651) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: per recipe PRSERV_HOST supportLianhao Lu2012-01-111-0/+8
| | | | | | | | | | [YOCTO #1126] Added per recipe PRSERV_HOST PRSERV_PORT support. (From OE-Core rev: d5b8caac0e7fc4b05c76b4d3da0508e2a53f28cd) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/PRService: Added export/import fuctions.Lianhao Lu2012-01-119-27/+260
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [YOCTO #1556] - Modified meta/class/package.bbclass and prserv.bbclass according to the change in PR service by adding PACKAGE_ARCH into the query tuple. - Added prexport.bbclass, primport.bbclass to export/import AUTOPR values from/to PRService. - Move PR service related common code to lib/oe/prservice.py. - Supported reading the AUTOPR values from the exported .inc file instead of reading it from remote PR service. - Created a new script bitbake-prserv-tool to export/import the AUTOPR values from/to the PR service. Typical usage scenario of the export/import is: 1. bitbake-prserv-tool export <file> to export the AUTOPR values from the current PR service into an exported .inc file. 2. Others may use that exported .inc file(to be included in the local.conf) to lockdown and reproduce the same AUTOPR when generating package feeds. 3. Others may "bitbake-prserv-tool import <file>" to import the AUTOPR values into their own PR service and the AUTOPR values will be incremented from there. (From OE-Core rev: 9979107d8eaf503efd921564385859b1e83dbb3c) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Incremental rpm image generation(Add config sample)Robert Yang2012-01-111-0/+7
| | | | | | | | | | | | Add the config sample for incremental image generation to meta-yocto/conf/local.conf.sample.extended [YOCTO #1651] (From OE-Core rev: 0df0399677a6677fc810e32e9275ee9e79021e9a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Incremental rpm image generationRobert Yang2012-01-113-13/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Incremental rpm image generation, the rootfs would be totally removed and re-created in the second generation by default, but with INC_RPM_IMAGE_GEN = "1", the rpm based rootfs would be kept, and will do update(remove/add some pkgs) on it. NOTE: This is not suggested when you want to create a productive rootfs For example: 1) Add the follow config option to a conf file: INC_RPM_IMAGE_GEN = "1" 2) bitbake core-image-sato modify a package bitbake core-image-sato The rootfs would not be totally removed and re-created in the second generation, it would be simply updated based on the "package". Implatation: 1) Figure out the pkg which need to be removed or re-installed, then use 'rpm -e to remove the old one. Use the rpm's BUILDTIME to determine which pkg has been rebuilt. 2) Figure out the pkg which is newly added, and use 'rpm -U' to install it. This only for the rpm based rootfs, the deb and ipk based rootfs would be done later. [YOCTO #1651] (From OE-Core rev: 575ba3c9e153a1d8ac228a99a03ca2df5fbca151) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Automatically start local PR service.Lianhao Lu2012-01-114-45/+123
| | | | | | | | | | | | | | | | | [YOCTO #1126] A local PR service will be started and stopped automatically along with the bitbake invocation/ternimation. This local PR service will be started only and if only when the PRSERV_HOST is set to 'localhost' and PRSERV_PORT is set to '0'. When started, the sqlite3 database is stored at "${PERSISTEN_DIR}/prserv.sqlite3" or "${CACHE}/prserv.sqlite3". (Bitbake rev: 9d8f45407c67ed0d3c4f820cf646de3c385067c7) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/PRservice: Added no_hist mode and export/import.Lianhao Lu2012-01-114-80/+263
| | | | | | | | | | | | | | | | | | | | | | | | | [YOCTO #1556] 1. Added the package_arch into the index to the DB table. Because the change in PACKAGE_ARCH will results in different checksum, and it is better to have seperate PR value domains for differnt PACKAGE_ARCH of the same pakcage. 2. Changed the PR service to operate in no history mode. In this mode, the for a given query tuple (version, pkgarch, checksum), the returned value will be the largest among all the values of the same (version, pkgarch). This means the PR value returned can NOT be decremented. 3. Added export function. For each (version, pkgarch) tuple, only the record with the maximum value will be exported. 4. Added import function. The record will only be imported if the imported value is larger than the value stored in the DB with the same (version, pkgarch, checksum) tuple. (Bitbake rev: 379567ee879dcdc09a51f7f1212bde1076147a6f) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "site/common-uclibc: Cache gl_cv_func_wcwidth_works"Richard Purdie2012-01-101-1/+0
| | | | | | This reverts commit a471d342424502de48f28c4f8297d490f2cd1443. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_tracking: update manual check infoDongxiao Xu2012-01-101-0/+1
| | | | | | | | | updated kexec-tools manual check information (From OE-Core rev: 4ab5ee52e4c47e8d913f2d5f86beac49e01d6a7b) Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* license.bbclass base.bbclass: support for 'or' operand in LICENSE and for ↵Andrei Gherzan2012-01-102-2/+46
| | | | | | | | | | | | | | | | | | SPDX license names A new function was defined in license.bbclass in order to correctly exclude packages where OE-Style licence naming is used. In this way licenses as GPL-3, GPLv3, GPLv3.0 etc will be excluded from a non-GPLv3 build. This function takes into consideration if 'or' operand is used. The function defined in license.bbclass is called in base.bbclass where packages are excluded based on INCOMPATIBLE_LICENSE variable. [YOCTO #1884] [YOCTO #1844] (From OE-Core rev: 28456593be0b7e15bb51595d547d7e5347cce24b) Signed-off-by: Andrei Gherzan <andrei at gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Add BBHandledException exception classRichard Purdie2012-01-103-4/+19
| | | | | | | | | | | | | | | | | | | | | | | We have a problem knowing when to show the user debug information and when not to since the code has already shown the user suitable information about why a failure is occurring. This patch adds a bb.BBHandledException exception class which can be used to identify those exceptions which don't need further explanation to the user. This patch uses this class for the bb.providers exceptions and ensures the command handling code correctly filters the exceptions meaning that "bitbake invalid" now shows an simple error message and not a python traceback. [YOCTO #1141 partial] (Bitbake rev: eac9249b40ae1e3aa21e016010c862664e59a8d4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/knotty: Show summary of warning/error messages shownRichard Purdie2012-01-101-2/+11
| | | | | | | | | | | Show a summary count of warning/errors messages shown to the user during the build and make it clear when an error exit code is being set. [YOCTO #1540] (Bitbake rev: 9943bad611a974e4d37a00c7a4de1752250370c5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: close files in apply_append()Paul Eggleton2012-01-101-0/+2
| | | | | | | | | | It's recommended practice to close files when finished with them and the code in this function was not doing this. (Bitbake rev: 470a160813ce6cf04f83258d46ded5c2ab8bc520) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: flatten: warn the user if output structure is incorrectPaul Eggleton2012-01-101-0/+38
| | | | | | | | | | | | | | | | | | If you flatten layers that have different directory structures you may not end up with a usable layer in the output directory - some files won't be picked up by BitBake. To try to avoid this problem, once flattening has completed, get the BBFILES entries that correspond to the layer from which the output layer's conf/layer.conf came from, and check through all of the .bb/.bbappend files in the output directory to see if any will not be referred to by BBFILES in the output layer. If any are found, show a warning to the user. (Bitbake rev: 8e4dc97614f2022855143b49d18795ca0352b237) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: flatten: allow specifying layers to flattenPaul Eggleton2012-01-101-8/+67
| | | | | | | | | | | | | | | | | | You can now optionally specify two or more layers to flatten into the output, rather than flattening all of the layers in the current configuration (but this is still the default behaviour if no layers are specified). Note that this means the output layer may still contain bbappends where the corresponding recipes are not present in the list of layers to flatten. There is also a caveat when a layer not being flattened would be "inbetween" the flattened layers (see the command help for details.) Implements feature request in [YOCTO #1564]. (Bitbake rev: 379b12107ec921b4458eda320078374a509164c1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_tracking_fields.inc: upgrade tcf-agentDexuan Cui2012-01-101-2/+2
| | | | | | | | | | Upgraded the field RECIPE_MANUAL_CHECK_DATE. Also changed the MAINTAINER to Lianhao who volunteered to take the recipe. (From OE-Core rev: 82329c13f891939c68ec26a60a9c0a25929cd584) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_tracking: Update Manual ChecksSaul Wold2012-01-101-25/+25
| | | | | | | (From OE-Core rev: 46955329638856a14200ee7ba10d40aad7c39899) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* task-core-tools: adapt to kexec-tools package splitAndrea Adami2012-01-101-2/+2
| | | | | | | | | | | * The recipe packages now kexec and kdump separately. * For standard purposes only kexec is needed. * Bump PR. (From OE-Core rev: fcd67dc6348df5a3435d4ae276d824e8e072b68d) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: split packaging of kexec and kdumpAndrea Adami2012-01-101-1/+6
| | | | | | | | | | | | | | | | * from meta-oe (originally from org.openembedded.dev) * There are no reasons to install kdump when only kexec is needed. * * In oe-core/meta there are no references to kexec-tools so * the recipes inn external layers rdepending on kexec-tools should be * fixed and rdepend on kexec and/or kdump. * * Bump PR. (From OE-Core rev: 1f40a5486f703684c5d1d7360ef3cbdf75577495) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: .pc files should go in the -dev packages for subpackagesColin Walters2012-01-101-2/+2
| | | | | | | The .pc files were ending up in util-linux-dev, not the correct subpackage like libuuid1-dev. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Enable fallocate and use CACHED_CONFIGUREVARSKhem Raj2012-01-101-4/+2
| | | | | | | | | | | | fallocate is implemented in eglibc 2.11 and all eglibc we use are greater than 2.11 so drop disabling it. Use CACHED_CONFIGUREVARS to specify scanf_cv_type_modifier=as (From OE-Core rev: 469eb3e1680443aa486d3a3c68e665e3388cc892) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* findutils: Use CACHED_CONFIGUREVARS to specify cached configure varsKhem Raj2012-01-101-2/+2
| | | | | | | | | | Since this feature is depending on wchar support we only cache is when we have libc-posix-clang-wchar enabled (From OE-Core rev: 783999bbe239b3a66cf87f7018a3087187c9bc11) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uclibc: Configure UCLIBC_HAS_WCHAR based on libc-posix-clang-wchar distro ↵Khem Raj2012-01-101-0/+1
| | | | | | | | | feature (From OE-Core rev: 80e6f9201ffa3b8f52f6d452c8657ec6fda4749c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: Introduce CACHED_CONFIGUREVARSKhem Raj2012-01-101-1/+1
| | | | | | | | | | | | | | | | | | This variable is for holding the cached configure variables to be specified in recipes. e.g. CACHED_CONFIGUREVARS += "ac_cv_foo=yes ac_cv_bar=no" This will make sure that the variables are not detected by configure. This is useful in cross builds where some features can not be detected correctly by configure and having it as a variables gives us capability to override it (From OE-Core rev: e48fd42e047f46399828a074c5125a0ce9c3f56f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: add shared library version info to libxml shared librariesMatthew McClintock2012-01-102-1/+26
| | | | | | | | | | | | | | | | | This fixes an issue with RPM where it checks version imformation for binaries linked against libxml and fails because it's missing info | error: Failed dependencies: | libxml2.so.2(LIBXML2_2.6.0) is needed by fmc-0.9.7+2-r2.1.ppce500mc | libxml2.so.2(LIBXML2_2.4.30) is needed by fmc-0.9.7+2-r2.1.ppce500mc | ERROR: Function 'do_rootfs' failed (see Note: fmc is just an example recipe/name (From OE-Core rev: d1f1fec5c6fe980aaf2c1f1dc2a0e737f4adf2dd) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc: Upgrade recipes 2.14 -> 2.15Khem Raj2012-01-1019-15/+172
| | | | | | | | | Add patch to provide __finite_sqrt functions for ppc (From OE-Core rev: 289d09176f8b6f66f6a7807b57f10e86939942f5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-modules: don't run modutils.sh if systemd is installedSteve Sakoman2012-01-102-2/+4
| | | | | | | | | systemd has its own mechanism for loading kernel modules at startup (From OE-Core rev: 553deffc8040afabd56b1c1d87a8a8d24bbae5d0) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-icon-cache.bbclass: add -f option to gtk-update-icon-cache in postinstSteve Sakoman2012-01-101-1/+1
| | | | | | | | | | | | | The gtk-update-icon-cache utility does not create a cache file if one does not already exist. Since some packages (notably gnome-icon-theme) do not ship a cache file by default, the results of the utility are not saved. Adding the force option writes out the cache even if there wasn't a default cache in the package. (From OE-Core rev: b3bb99c6faaf5c1613246309fd05cd95c39c77f4) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: change permissions of dbus-daemon-launch-helper to 4755Steve Sakoman2012-01-101-1/+3
| | | | | | | | | | | | | | With current permissions of 4754 on systemd systems various services will fail to activate with "helpful" error messages of the type: 2000-01-01T00:00:25+00:00 omap3-multi dbus[178]: [system] Activated service 'org.freedesktop.nm_dispatcher' failed: Failed to execute program /usr/libexec/dbus-daemon-launch-helper: Success (From OE-Core rev: 7b1e227bf28c9d4f3bb16af4d9ac21265e88a3f1) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove last remnants of kernel26 MACHINE_FEATURESSteve Sakoman2012-01-103-4/+3
| | | | | | | | | There is no reason to continue to carry this feature (From OE-Core rev: f1193e077d187b9ce18ae0686b1a1f0f9832036d) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libusb-compat: keep *.la in base_libdirAndreas Müller2012-01-101-2/+1
| | | | | | | | | build-tested from scratch in angstrom environment. (From OE-Core rev: 4fa337fe932230b43d7006cdd8b44dfa05501bbe) Signed-off-by: Andreas Müller <schnitzeltony@gmx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-15 04:17:02 +0000