summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: Update users of getVar/setVar to use the data store functions directlyRichard Purdie2011-11-2724-198/+196
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* getVar/setVar cleanupsRichard Purdie2011-11-2727-159/+152
| | | | | | | | | Complete the bb.data.getVar/setVar replacements with accesses directly to the data store object. (From OE-Core rev: 2864ff6a4b3c3f9b3bbb6d2597243cc5d3715939) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript: Ensure we run reautoconfRichard Purdie2011-11-271-16/+16
| | | | | | | | | | Avoding the autoreconf with a hardcoded do_configure is bad practise since it can hide various errors. This patch ensures we do use the standard do_configure. (From OE-Core rev: 54c4b4fd10c104641bb7ae087b2230aa6c6085f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript-native: Ensure the sys/time/h fix is applied for native buildsRichard Purdie2011-11-271-0/+1
| | | | | | | | | | On my system, the sys/time.h header is in a subdir off /usr/include which causes a build failure. Apply the target CFLAGS fix to native builds as well to address this. (From OE-Core rev: 67176378266767cd0cca4f8ecafa865907ca4bdd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript: Really fix parallel make raceRichard Purdie2011-11-272-1/+20
| | | | | | | | | | | | | There continue to be parallel make race issues showing up on the autobuilder. This patch removes some potential sources of these. The rm is unrequired since we're using cp -f. The || true ensures that if we did race against someone it becomes harmless. [YOCTO #1202] (From OE-Core rev: 32840cd95fcde92433fbb0271b82d0f4048a823a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/adt-manual/adt-prepare.xml: Fixed bad URL for edison tarballScott Rifenbark2011-11-251-1/+1
| | | | | | | | | | The URL for the edision tarball was old and had been locked down in the manual too early. It changed and now this fixes it. (From yocto-docs rev: c1668e41babd7ef592dc26271943c99bacc3f181) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/dev-manual/dev-manual-newbie.xml: Updates to Bugzilla useScott Rifenbark2011-11-251-30/+45
| | | | | | | | | | | | I updated the Bug Tracking section to include rudimentary use of Bugzilla for entering a new bug. Fixes [YOCTO #237] (From yocto-docs rev: 8f2702444812c9dc25195340acebbaae15cd59d7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/poky-ref-manual/ref-variables.xml: EXTRA_IMAGEDEPENDS added.Scott Rifenbark2011-11-251-0/+19
| | | | | | | | | | New glossary entry added. Reported-by: Darren Hart. (From yocto-docs rev: 03845586f7331630bd1d9b5eebb9df9eccbd05a0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: BB_NUMBER_THREADS and PARALLEL_MAKE suggestionsScott Rifenbark2011-11-254-14/+11
| | | | | | | | | | | | | | | Text that suggests setting the BB_NUMBER_THREADS and PARALLEL_MAKE variables to speed build time has been updated to suggest a setting of twice the number of host cores supported. The 2x number came to light through a discussion on the project mailing list initiated by Robert P. J. Day. Reported-by: Robert P. J. Day (From yocto-docs rev: 1846b41a595b7bd905ca828eaa04112d1533d7a1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/adt-manual/adt-prepare.xml: Updated link to machinesScott Rifenbark2011-11-251-1/+1
| | | | | | | | | I replaced the link with the URL that uses 'downloads.yoctoproject.org....' (From yocto-docs rev: fef7ca4f2a549fabc1932a40a46cf0c6c834074f) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documenation/adt-manual/adt-prepare.xml: Fixed toolchain tarball nameScott Rifenbark2011-11-251-1/+1
| | | | | | | | | | | the name was off. It was 'yocto-eglibc-x86_64-i586-toolchain-1.1.tar.bz2'. Really, the name is 'poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2'. (From yocto-docs rev: 3d051f3e814f27f661ce153b66735f75a4152d04) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/adt-manual/adt-prepare.xml: Updated link to toolchain and infoScott Rifenbark2011-11-251-2/+2
| | | | | | | | | | | I updated the link to be 'download.yoctoproject.org/releases/yocto/yocto-1.1' I also fixed the text that indicated 'i586' as a directory for the 32-bit machines. The real directory name is 'i686'. (From yocto-docs rev: fc08acdce64bac7c2b3d4689e16cf06e70f6cbe5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Added footnote element to the stylesheetsScott Rifenbark2011-11-255-0/+30
| | | | | | | | | | | | During development, a footnote was added to the Development manual. In order to get the footnote to display correctly, I had to introduce a footnote element in the style sheet. This commit propogates the style to the other manual CSS sheets. (From yocto-docs rev: 0439b46620125f2cb26dff4e8c79fc479205133a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/yocto-project-qs/yocto-project-qs.xml: fixed broken linkScott Rifenbark2011-11-251-1/+1
| | | | | | | | | | "www" was messing up the link. Removed it. Reported-by: William Mills (From yocto-docs rev: ae7074325c78385684c51c06e8a27686e6fa1d05) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/dev-manual: Edits from Tom Zanussi.Scott Rifenbark2011-11-254-15/+28
| | | | | | | | | | | Tom Zanussi provided a review up through part of the "model" chapter. I have implemented his comments mosty verbatim. Reported-by: Tom Zanussi (From yocto-docs rev: 693d4fadd4b34ffef9953fb1850d381ff7c028a3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Changed all manual links to point to "latest"Scott Rifenbark2011-11-2525-124/+124
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are many references to YP documentation throughout the YP manual set. They used to have hard-coded links to the current release (e.g. yoctoproject.org/docs/1.1 for Edison). This created a situation where if you went to a document on the website and clicked on a external reference to another manual, you would redirect to the current manual on the website. Really, you would want to go to the latest manual, which is one that is under development. Changing the links to "yoctoproject.org/docs/latest" makes the tip of master, which is used for devloping the next release, always have references to the manuals being developed and not back to the stable released set of manuals. This "latest" and "current" scheme for the links is not perfect. What has to happen when the latest set of the manuals freezes and becomes the next stable release, all the links in the docs will need to be changed from "latest" in the URL to the new release number. So for example, all the "latest" occurences would need to be changed to "1.2". Then for the next cycle as development begins again, the links need to be infused with "latest" again. (From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/yocto-project-qs/yocto-project-qs.xml: Updated packages sectionScott Rifenbark2011-11-251-22/+50
| | | | | | | | | | | | | | | Split the instructions for getting the packages needed for Yocto into sections that specifically support Ubuntu, Fedora, and openSUSE. Also, added a couple packages to openSUSE. I did not implement a suggested change to include a note indicating future support of the dash shell since it probably is not good policy to document plans as they change. Reported-by: Darren Hart (From yocto-docs rev: 3dbbb22ccdda1a7e809e61e19f5d04ab26e3499c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/poky-ref-manual: Minor wording fixesRobert P. J. Day2011-11-252-6/+6
| | | | | | | | | Robert identified several wording issues. Fixes applied. (From yocto-docs rev: 9c1ed58a1ecdd620246970419ed58b53f95cf2ec) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/poky-ref-manual/introduction.xml: Fixed broken linkScott Rifenbark2011-11-251-1/+1
| | | | | | | | | | Robert identified this broken link to the stable Yocto Releases. As Reported by: Robert P. J. Day (From yocto-docs rev: e42a501df2ca44030f99f017b8c532b03db62f55) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Standardized on spelling of BitBakeRobert P. J. Day2011-11-255-6/+6
| | | | | | | | | | Robert found five instances where I missed the correct usage of "BitBake." (From yocto-docs rev: 0819076e8677accd157497ed4fa33ebab2528044) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ofono: Fix missing python dependency and package tests separatelyRichard Purdie2011-11-253-2/+6
| | | | | | | | | | | | | We need to ensure there is a python dependency for the ofono python test scripts. To do this without introducing the dependency unnecessarily for the core ofono functionality, this patch splits the tests into a separate package too. [YOCTO #1705] (From OE-Core rev: f699cb48c7f379f97623f1f244b0b6c5875d7497) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/siggen.py: Don't backtrace if the taskhash data isn't presentRichard Purdie2011-11-251-2/+2
| | | | | | | | | | This allows the code to safely fall back to dumping the basehash data if the taskhash data isn't present for some reason. We could effecitvely obsolete the runtime option and use this approach instead exclusively. (Bitbake rev: 5ace320ccc01f4e326f90b7ba060dcbff3380dca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update and fix bitbake-runtaskRobert Yang2011-11-251-66/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since bitbake switched back to the fork instead of the exec model, it no longer used bitbake-runtask and the code has suffered some bitrot. bitbake-runtask is a useful tool for excuting the task without the scheduler of bitbake, so that the external tool can invoke it easily. It also provides a useful example of how to invoke exec_task() with low overhead without a lot of the bitbake threading/UI overhead. Significant changes: * This patch changes the argument order so that the commonly used and mandatory arguments come first. * The taskhash file and dryrun options are now optional * It now uses the bitbake logging mechanisms to provide processed logging output to the console. * The process handling to do with stdout/stderr redirection are removed since they're no longer required. [YOCTO #1229] RP: Logging updates to the patch based on Roberts original patch Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Nothing uses USERNAME, remove it - can cause sstate-cache conflictsMatthew McClintock2011-11-251-1/+1
| | | | | | | | | | USER is the correct variable to use, also this can affect sstate cache as well. (From OE-Core rev: 0f446c29f10fd83228619e05ddec29fdc29188b3) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Nothing uses USERNAME, remove it - can cause sstate-cache conflictsMatthew McClintock2011-11-251-1/+0
| | | | | | | | | | USER is the correct variable to use, also this can affect sstate cache as well. (Bitbake rev: d7f9edda65dae2e046871afa275c5a51dff48fc4) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-target.inc: add the symbol link /lib/cppDexuan Cui2011-11-242-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When I was trying self-hosted-image, eglibc's do_install failed in the target: ERROR: cannot stat bootparam_prot.h: the cause is: rpcgen doesn't work properly: rpcgen can't exec /lib/cpp since it doesn't exist. According to http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/lib.html: "if a C preprocessor is installed, /lib/cpp must be a reference to it, for historical reasons. The usual placement of this binary is /usr/bin/cpp". Typical distros, like Ubuntu, openSuSE, Fedora and RHEL, all comply with the rule. Actually in meta/recipes-devtools/gcc/gcc-package-target.inc, we do try to package ${base_libdir}/cpp: FILES_cpp = "\ ${bindir}/${TARGET_PREFIX}cpp \ ${base_libdir}/cpp \ ${libexecdir}/gcc/${TARGET_SYS}/${BINV}/cc1" But unluckily we didn't create a symbol link in do_install. This patch adds the symbol link. (From OE-Core rev: 58fb9fbce2af05a469691390e75aebb2de16ca96) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site/x86_64-linux: add cvs config variablesNitin A Kamble2011-11-241-0/+3
| | | | | | | | | | | | | | configure of cvs packages was failing on the meta-toolchain for a x86_64 target. Configure error reported: checking whether printf supports %p... configure: error: cannot run test program while cross compiling This fixes [YOCTO #1781] (From OE-Core rev: 061818adbea1af9e98fe0fdf81b21f1e7f210c00) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: We only care about the absolute value of baselibRichard Purdie2011-11-241-0/+1
| | | | | | | | | | | | | | The value of baselib can be constructed in several different ways and from a sstate perspective we don't care how it was made up, we only care what the final value is. This uses the new functionality in bitbake to ensure we only include the value of baselib and not any intermediate dependencies. [YOCTO #1583] (From OE-Core rev: c38567894ebc31ac977f2bc89a076d0380bddcf8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi-ui: Fix packaging and conflict with the avahi recipeRichard Purdie2011-11-241-3/+29
| | | | | | | | | | | | | | | | | | We need to remove the files from avahi-ui which conflict with the avahi recipe. If we don't do this they trigger packaging warnings and can also overwrite files in the sysroot unexpectedly causing build failures (if X depends on avahi, it expects avahi's files to stay there, not disappear as avahi-ui build/stages). This patch cleans up the packaging although I wish there were an alterantive to the do_install which makes my eyes bleed. [YOCTO #1770] [YOCTO #1722] (From OE-Core rev: 95b383781f875a0f10e5c1de039289bb89e421dd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc.inc: Remove EGLIBPARALLELISM from deps for EXTRA_OEMAKEMatthew McClintock2011-11-241-0/+1
| | | | | | | | | | Without this simply changing the number of threads via PARALLEL_MAKE can invalidate sstate-cache (From OE-Core rev: 45140c860272fa4b610805d4dacadcf9201c3e35) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patch.bbclass: Add PATCHRESOLVE to excluded vars for generating sstate-cacheMatthew McClintock2011-11-241-1/+1
| | | | | | | | | | The method of resolving the patch should not effect the sstate-cache signature. (From OE-Core rev: b64cbe0b511de8d8943ce34cbb4901239d9f0cb0) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+: Have gtk+ pick up ${NM} from the environmentXiaofeng Yan2011-11-242-1/+16
| | | | | | | | | | when gtk+ configures, it should pick up ${NM} from the environment \ if it is defined, instead of just looking for "nm". (From OE-Core rev: 7cb5063d8bc59534dc64b19164cb9bdf0c04c68b) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tslib: Set open mode for ts_calibate.cXiaofeng Yan2011-11-242-2/+33
| | | | | | | | | | | | | | | Get patch from: http://permalink.gmane.org/gmane.comp.lib.uclibc.buildroot/27614 There is a potentially "unsafe" use of open(). Ubuntu 8.10+, for instance, by default enables the compiler flag -D_FORTIFY_SOURCE=2 \ which throws an error of ts_calibrate.c. To fix this, \ set a mode in the open() call, patch patched ts_calibrate.c \ to set 0644 (S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH) and it compiles fine (From OE-Core rev: 61928384b91f7328aaa72c6d1299d8598c24574d) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Flush old logs by change the DB_CONFIGMei Lei2011-11-242-2/+15
| | | | | | | | | | | Fixes [YOCTO #1174] Rpm logs will grow indefinitely, so change the config to flush those old logs. (From OE-Core rev: e2c4dff079722f256ddcab9630b5b3f8f6421cc9) Signed-off-by: Mei Lei <lei.mei@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc_2.13: update SRCREVKang Kai2011-11-243-182/+5
| | | | | | | | | | Update eglibc 2.13 SRCREV to 15508, just to sync with upstream Remove glibc_bug_fix_12454.patch, because it is already merged. (From OE-Core rev: e364b04a34d7c2a95145799773821e82b8677e78) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-passwd: add Upstream-Status to patches, remove unused patchScott Garman2011-11-243-27/+22
| | | | | | | | | mysql.patch is not used by the recipe anymore, so delete it. (From OE-Core rev: a60449f6110bc86dd0d976413c169bafc0ebcada) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dosfstools: add Upstream-Status to patchesScott Garman2011-11-247-0/+44
| | | | | | | (From OE-Core rev: 735a3e5d3399e29e4d6fa82dabbdd1687eaa29e9) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Set BB_CONSOLELOG so we log console messages by defaultRichard Purdie2011-11-241-0/+2
| | | | | | | | | | | | | | The console log is often helpful for debugging issues. Difficult to reproduce bugs would benefit from a log being generated by default as it may be difficult to come by after the fact. Log to ${TMPDIR}/cooker.log.${DATETIME} by default. [YOCTO #1771] (From OE-Core rev: 4b916ce59bf88ca92b034b2acaddee6130155e46) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Use bb.plain to print the build headerRichard Purdie2011-11-241-1/+1
| | | | | | | | | If we just use print, the bitbake logging functions don't see the message and it can get lost if bitbake is for example logging messages to disk. (From OE-Core rev: 73a3d0d337e26c2be89c215efb8a2c3dd5d5994d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* data/siggen: Add vardepvalue mechanism to allow the variable dependency code ↵Richard Purdie2011-11-242-11/+15
| | | | | | | | | | | | | | | | | | | | | | | to be forced to specific values We have a problem if we want to inject specific information into the variable dependency code. There are cases for example where we want a dependency on the value of X but it doesn't matter how X was constructed or what dependencies it might have had, we only care about the absolute value. With the current code, its near enough impossible to do this. This patch adds such a mechanism so the user can trigger this with code like: baselib[vardepvalue] = "${baselib}" It also refactors some of the code so we do variable lookups once instead of doing this in two different functions. [YOCTO #1583] (Bitbake rev: 6c879b44ccf42dc73fe4467076e114700d7ba81b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fetch2: Improve uri_replace to handle paths with no trailing '/'Richard Purdie2011-11-241-3/+10
| | | | | | | | | | | | | | | | | | | | | | Currently if you specify a mirror like: file://.* http://linux.freescale.net/yocto/sstate-cache it won't work as you expect whilst: file://.* http://linux.freescale.net/yocto/sstate-cache/ will since it has the trailing slash. This patch handles both cases correctly. It also adds some debug to the uri_replace function since its near impossible to debug it without some kind of output. [YOCTO #1578] (Bitbake rev: a0246bf09c93bb657eaf6ba61d090b247ed33640) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* knotty: Add support for logging the console to logfileRichard Purdie2011-11-241-0/+6
| | | | | | | | | | | | The BB_CONSOLELOG variable is used to specify the console log file to use. This means people can look up things that happened during a build by may have scrolled off the screen. [YOCTO #1771] (Bitbake rev: a34ff490a46577a64345365fa1ac39c48d0861cd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqueue.py: Fix debug message to reference the correct taskRichard Purdie2011-11-241-1/+2
| | | | | | (Bitbake rev: 035c673c463ca450245acf824e7b7e8f889bdc89) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fetch2/local: Don't default to files in DL_DIR for file:// urlsRichard Purdie2011-11-241-3/+1
| | | | | | | | | | | | | | | Defaulting to any file in DL_DIR as the first match for a file:// url doesn't make much sense and can lead to unexpected results. This patch changes the logic so this is the last fallback location instead. Whether it should be using DL_DIR at all for this is a good question but something for another patch. [YOCTO #1710] (Bitbake rev: 5597a68fac0954c682b67471722c2643e2415f99) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Avoid relinking when cross compiling, its pointlessRichard Purdie2011-11-243-2/+105
| | | | | | | | | | | | | | | | | | | | There is no point in having "executable" binaries in the .libs directory linked with different rpaths to the target which could concivably be run on the build system when cross compiling. This patch removes the extra rpaths ($compile_rpath) so that the output from the "link" stage can be used on the target. We can then avoid having to "relink" during the install stage. This saves some build time (do_install is over 2 minutes faster for pulseaudio). This patch also removes an annoying "seems to be moved" warning which is totally bogus in the sysroot case. (From OE-Core rev: 0a1dedeb8eea4e230b47d1516b3e6e90495fe49d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apt: Fix locale header and hardcoded libname issuesRichard Purdie2011-11-236-10/+104
| | | | | | | | | | | | | apt wasn't building on modern libc/compiler combinations due to missing header includes. The libcpp version was also being hardcoded, this patch generates it dynamically to work on different host systems which no longer have this. (From OE-Core rev: ca8237ee51053d70b5e7579c224a824db2be76b2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* directfb: change check sumXiaofeng Yan2011-11-231-5/+3
| | | | | | | | | | Change check sum of directfb. The previous checksum was incorrect when it was added due to a corrupted download on the submitter's system. (From OE-Core rev: 7056ea9b1eb5ff358c1f8d2b949597e4e98f3a2b) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siggen.py: sort task hash depedencies with basepathMatthew McClintock2011-11-231-11/+14
| | | | | | | | | | | | | | | Without this patch the tash hash dependencies can be in a order that is dependent upon directory/filesystem layout. With this change the data is sorted the same regardless. Without this the dependent hashes could be in different orders on different systems and consequently final md5 hash would differ as well even though nothing else changed. (Bitbake rev: 9a2029899c946ce9aa8adbc85f2cfe7a85b92182) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: print out symmetric difference when comparing sigsMatthew McClintock2011-11-231-0/+4
| | | | | | | | | | This is useful for really longs lists to pinpoint what has actually changed (Bitbake rev: f1eb6d3dcc10c42bb09383a87bde3afa69bc6ed9) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqueue.py: Ensure we fully process the covered listRichard Purdie2011-11-231-3/+4
| | | | | | | | | | | | | | | The existing looping code can mask an existing "found = True" by forcing it to False each time. This can lead to dependency lists not being fully searched and results in dependency errors. An exmaple of this was the autobuilder building linux-yocto from sstate but then rebuilding some of the recipe's tasks for no apparent reason. Separating the logic into two variables solves this problem since any "found = True" value is now always preserved. (Bitbake rev: 61017fc5d30b7a13308d038872ec92efc1a84cef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-04 14:08:57 +0000