summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ref-manual: Updated the autotools class.Scott Rifenbark2014-10-181-2/+1
| | | | | | | | | | Needed to change wording to state that the class uses out-of-tree builds. (From yocto-docs rev: 2fbaeba33988e14a97d5946f7e714a1bbc5a3ccb) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, ref-manual: Updated 1.7 migration section with review commentsScott Rifenbark2014-10-183-7/+7
| | | | | | | | | | Applied the second round of review edits from Paul Eggleton. Minor fixes. (From yocto-docs rev: 2c7c45c8f09b724e92e8b59fe47834226b44b4fb) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, dev-manual: Applied migration review edits.Scott Rifenbark2014-10-185-133/+103
| | | | | | | | | | Applied the full set of first draft revision edits for the new migration section for 1.7. Comments from Paul Eggleton. (From yocto-docs rev: 90586addbc719ecaf7c768b267adf0e988e27b74) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: Updated build history figureScott Rifenbark2014-10-182-0/+0
| | | | | | | | | | | | | The figure needed to be updated to reflect that build-id.txt is now part of the tree and not build-id. The publication scheme dictates that figures are kept in individual manuals and in the mega-manual figures directory. (From yocto-docs rev: 0711a3e41c42eb058db25ff2ea7f1c0982e06963) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added new migration section for the 1.7 release.Scott Rifenbark2014-10-181-0/+298
| | | | | | | (From yocto-docs rev: 5b06b29f7f9e53db7b885795c2e11e1eccfc98df) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the build history section for build-id.txtScott Rifenbark2014-10-181-2/+4
| | | | | | | | | | | This file is what is written now rather than build-id. I changed the file name and noted that it also contains the full build header information as written out by BitBake during the build. (From yocto-docs rev: 7e55b4b5f9e27f6ac5d8f1eab4923bf1b8a712c6) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Updated the list of linux-yocto kernelsScott Rifenbark2014-10-181-3/+3
| | | | | | | | | | | I removed the linux-yocto 3.4 kernel from the list in the section describing which kernels we support. Also, added the 3.17 linux-yocto kernel to the list. (From yocto-docs rev: 41f57a9abe1201ed2fb657f8441c97f86f75200a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added cross-reference.Scott Rifenbark2014-10-181-1/+1
| | | | | | | (From yocto-docs rev: f64cc93d364a04c51f2c685fffad7a124349474a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the module_autoload variable.Scott Rifenbark2014-10-181-38/+8
| | | | | | | | | | | This variable has been replaced by the KERNEL_MODULE_AUTOLOAD variable. I updated the description to note that and to provide a cross-reference to the new variable. (From yocto-docs rev: 8b2f464f7d100db1c585ccc62d7cab89f7f7b164) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added new KERNEL_MODULE_AUTOLOAD variable.Scott Rifenbark2014-10-181-0/+50
| | | | | | | | | Added this description to the variables glossary. (From yocto-docs rev: 3da322f92d5028e96422e0c1f5df78b285f2355e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added new KERNEL_MODULE_PROBECONF variableScott Rifenbark2014-10-181-0/+59
| | | | | | | | | Added this new variable to the variable glossary. (From yocto-docs rev: d2d75631777f6cef3472bde428ed65419c99457e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated module_conf variableScott Rifenbark2014-10-181-6/+13
| | | | | | | | | | | | | This description was a bit confusing with the way the general syntax was described so I re-wrote it a bit. Also, added the requirement that if you use module_conf for a given <modname>, then you must also include the <modname> as part of the new KERNEL_MODULE_PROBECONF variable. (From yocto-docs rev: 15b7819a0d9946ad6565576a6f28897e2dd724f9) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0869Yue Tao2014-10-182-0/+34
| | | | | | | | | | | | | | | The field_end function in libavcodec/h264.c in FFmpeg before 1.1.2 allows remote attackers to have an unspecified impact via crafted H.264 data, related to an SPS and slice mismatch and an out-of-bounds array access. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0869 (From OE-Core rev: 464123172c92d92fa08e2125c04653590ad654c7) Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-4358Yue Tao2014-10-182-0/+146
| | | | | | | | | | | | | | libavcodec/h264.c in FFmpeg before 0.11.4 allows remote attackers to cause a denial of service (crash) via vectors related to alternating bit depths in H.264 data. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-4358 (From OE-Core rev: 6a029bee3da097b9ed8c421fcd5ea61cd1a31b34) Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtools: fix broken /usr/bin/lzWenlin Kang2014-10-182-1/+26
| | | | | | | | | | | | | | | | | | | | | | | When build fs with mtools-3.9.9, has file /usr/bin/lz in rootfs, it is the symlink to uz: root@qemu3:~# /usr/bin/lz -sh: /usr/bin/lz: No such file or directory $root@qemu3:~# ls -l /usr/bin/lz lrwxrwxrwx 1 root root 2 Jul 18 18:07 /usr/bin/lz -> uz root@qemu3:~# uz -sh: uz: command not found But the uz isn't actually exist, so the result is that lz is a broken symlink. The root cause is that uz hasn't been installed when install-scripts. (From OE-Core rev: 7308da9ccd4b8b9b5077aacd0442be28a6c73c61) Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg_1.4.7: add package config libusbKai Kang2014-10-181-0/+1
| | | | | | | | | | | | | If build gnupg 1.4.7 after libusb-compat, it shows warning: WARNING: QA Issue: gnupg rdepends on libusb-compat, but it isn't a build dependency? [build-deps] Add package config libusb to fix it. (From OE-Core rev: e1c77392143e538a2305f63ee3add611ec66e877) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: upgrade to 1.0.1jRoss Burton2014-10-181-2/+2
| | | | | | | (From OE-Core rev: 390916b8400a46088c71183aef6e17b947cf4b74) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* readline: Security Advisory - readline - CVE-2014-2524Kai Kang2014-10-182-0/+45
| | | | | | | | | | | | | | The _rl_tropen function in util.c in GNU readline before 6.3 patch 3 allows local users to create or overwrite arbitrary files via a symlink attack on a /var/tmp/rltrace.[PID] file. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-2524 (From OE-Core rev: 0e95eef8817f51504dcc50d855dcbef172cfc897) Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg: CVE-2013-4242Kai Kang2014-10-182-0/+63
| | | | | | | | | | | | | | | | GnuPG before 1.4.14, and Libgcrypt before 1.5.3 as used in GnuPG 2.0.x and possibly other products, allows local users to obtain private RSA keys via a cache side-channel attack involving the L3 cache, aka Flush+Reload. Patch from commit e2202ff2b704623efc6277fb5256e4e15bac5676 in git://git.gnupg.org/libgcrypt.git (From OE-Core rev: d1e0f3e71ce9978ff0fc94d71e67b528dad84c5c) Signed-off-by: Yong Zhang <yong.zhang@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Fix up white space lost in last commit.Peter Urbanec2014-10-181-20/+20
| | | | | | | | | | | Commit e9672387 split one long line into a multi-line string, but in the process white space between words was lost. This results in badly formatted output when this message is printed. (From OE-Core rev: b145374c0a498de0160a9b81f50ce0066ab14862) Signed-off-by: Peter Urbanec <openembedded-devel@urbanec.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: specify func dirs for sstate_hardcode_pathWenzong Fan2014-10-181-0/+5
| | | | | | | | | | | | | | | | | | | | | For some recipes that inhrient cmake, the ${B} may be removed by cmake_do_configure() while sstate_hardcode_path() running, this causes build errors: Exception: OSError: [Errno 2] No such file or directory: \ '/path/to/build' The function sstate_hardcode_path() called command: $SSTATE_SCAN_CMD which extended as "find ${SSTATE_BUILDDIR} ..." So the proper function dirs could be ${SSTATE_BUILDDIR}. (From OE-Core rev: a949943e622b08485fc7632a0a743bc009079c67) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* file: add wrapper to nativesdk-fileHongxu Jia2014-10-181-0/+5
| | | | | | | | | | | | | | | | | | "file" command in exported SDK doesn't work: ... $ file sysroots/ file: could not find any valid magic files! ... In oe-core commit 68d548cbae729eaea8ce1403dc95ff63c4a7375c, it added wrapper to file-native. Do the same thing for nativesdk-file. (From OE-Core rev: 69a3ab38d1c725c2b575065739cae4a3b45015a2) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: avoid screen sessions being killed on disconnect with systemdPaul Eggleton2014-10-181-0/+1
| | | | | | | | | | | | | | | Tell systemd just to kill the sshd process when the ssh connection drops instead of the entire cgroup for sshd, so that any screen sessions (and more to the point, processes within them) do not get killed. (This is what the Fedora sshd service file does, and what we're already doing in the dropbear service file). (From OE-Core rev: 3c238dff41fbd3687457989c7b17d22b2cc844be) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: force off_t size to 8 to enable large file supportPaul Eggleton2014-10-181-0/+3
| | | | | | | | | | | | | | | If DISTRO_FEATURES contains "largefile", force the size of off_t to 8 as a workaround for having ac_cv_sizeof_off_t=4 on 32-bit systems. In future we will likely drop the value from the site file, but for now this is a slightly safer fix. Fixes [YOCTO #6813]. (From OE-Core rev: a8216030ee6c65531de8fbf3eed878a345a94edc) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic/bootimg-pcbios.py: checking the existance of syslinuxHongxu Jia2014-10-181-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | While syslinux not existed in $bootimg_dir, there was a error: $ wic create directdisk -e core-image-minimal ... |Creating image(s)... |Error: exec_cmd: install -m 444 /home/jiahongxu/yocto/ build-20141010-yocto/tmp/deploy/images/qemux86-64/syslinux/ ldlinux.sys /var/tmp/wic/build/hdd/boot/ldlinux.sys returned '1' instead of 0 ... Add checking for the existance of syslinux to fix this issue. If syslinux didn't exist in anywhere, prompt user to build it. [YOCTO #6826] (From OE-Core rev: c2d4364d9fbbda64598f0a3eb0b0890932bb7742) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-10-111-1/+1
| | | | | | (From OE-Core rev: fcbd1b19383daf5e160a864df1418130da01be28) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetcher: fix getVar call due to incorrect argument datatypeAlejandro Hernandez2014-10-111-1/+1
| | | | | | | (Bitbake rev: 2ac33aac3446cb12227f1b8daa5f27f417c9bb9e) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: backport patch for gcc bug 61144Saul Wold2014-10-112-0/+32
| | | | | | | | | | | | | | This fixes gcc bug 6144, which in my case exhibited itself as a kernel module that failed to load. This was because static platform_data structures were being corrupted with the optimiser being set to any value other than -O0. Originally-submitted-by: Peter Urbanec <openembedded-devel@urbanec.net> (From OE-Core rev: 365221f7285c0e392f573deaab3b1e00b12bc293) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_deb: skip pre/postrm scripts on upgrade, write only one shebangAndreas Oberritter2014-10-111-2/+15
| | | | | | | | | | | | | | | | Trying to upgrade busybox removing symlinks but update-alternatives need these links (sed, cut, tail, etc) in order to work. Adding test to avoid this scripts on upgrade fix the problem, same solution are found in package_rpm class. [YOCTO #6768] (From OE-Core rev: 7b9161dd0c475cca6ea7eb507f7c3c51869eb493) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa_git.bb: Fix fetch and license errors.Randy Witt2014-10-111-3/+2
| | | | | | | | | | Without these changes mesa_git.bb can't be enabled as the PREFERRED_VERSION due to build breakage. (From OE-Core rev: 04f48ad3fab4e21a23c46b90f6a62269a1cf1ee7) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-10-101-1/+1
| | | | | | (From OE-Core rev: 1d2a7e0d4ab91b5ad7d0a1c300ab1da7db49520d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_do_shlibs: Look for provider in the path thats in shlib_provider ↵Khem Raj2014-10-101-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dictionary shlib2 code puts the information about path where a provider will be found. e.g. {'/usr/lib/llvm3.3': ('libllvm3.3-llvm-3.3', '3.3')} This is obtained from new shlib2 pkgdata from llvm3.3/3.3-r0/pkgdata/shlibs2/libllvm3.3-llvm-3.3.list However when we search for NEEDED libraries we ignore the key above which is the path where the provider library is installed and instead just seach in libdir and base_libdir and hence libraries which are not in above standard search paths gets ignored even if they appear in DT_NEEDED sections and a note is emitted NOTE: Couldn't find shared library provider for libLLVM-3.3.so, used by files: .... IMO this note should actually become an error since if we do not have all DT_NEEDED libraries in image the system is dysfunctional. This patch extracts this libpath from key and add it to seach paths when looing for a provider of a shared library [YOCTO #6798] Change-Id: Ie5f08632e37ba8d3439c8aaae33bc68b8996792f (From OE-Core rev: bf8472274ac1e9a35f8cbc82357da6c95b396759) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-10-101-1/+1
| | | | | | (From OE-Core rev: 5d0aac8d85d927667c4c26cab53132ff4fa465ff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-10-101-1/+1
| | | | | | (From OE-Core rev: 1216427655dd67d49100cd7bfa50563e2f5965f7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ncurses: enable-pc-files requires PKG_CONFIG_LIBDIR existedRobert Yang2014-10-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed ncurses.do_configure: configure: WARNING: did not find library /path/to/tmp/sysroots/qemuarm/usr/lib/pkgconfig And then anyone requires ncurses.pc will fail. The configure.in checks: [snip] if test -n "$PKG_CONFIG_LIBDIR" && test -d "$PKG_CONFIG_LIBDIR" ; then [snip] Create PKG_CONFIG_LIBDIR in do_configure will fix the problem. We can reproduce the problem by: Set SSTATE_DIR=/path/to/sstate-cache 1) In build1, make sure everything is ready in SSTATE_DIR $ bitbake ncurses 2) In build2, rebuild ncurses only: $ bitbake ncurses -ccleansstate && bitbake ncurses Then we will see the warning in log.do_configure. (From OE-Core rev: ea4010c8398745736b0c22ed037604db8fc43212) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "meta-yocto: make 3.17 the preferred qemu kernel version"Richard Purdie2014-10-101-7/+7
| | | | | | | | | | | | | | | | | | 3.17 has problems with: a) CONFIG_USB_WACOM -> CONFIG_HID_WACOM b) The wacom driver no longer working with qemu c) The USB stack being missing on arm and ppc and these are just the issues we know about. Switch back to 3.14 until 3.17 is fixed. This reverts commit 6a56492f3ae5e2a7e4d5b80169710a0eab87c0e2. (From meta-yocto rev: 60ff51c7a53865ac6d6f04119264982fc6a7fa4e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, template: Permalinks for QA errors and warningsScott Rifenbark2014-10-103-40/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updated the ref-qa-checks.xml chapter so that each QA warning or error message would generate a permalink that is suitable for searching from the poky codebase. To implement this, I had to embed an id marker in the <para> tag that precedes each <code></code> tag pair. The 'xxx' string of the id is the leaf portion of the permalink. This creates the following tag construct: <para id='xxx'> <code> some-warning-or-error-message </code> </para> The permalink is generated with the help of the new qa-code-permalinks.xsl file, which triggers on the <para><code></code></para> construct. This new file resides in documentation/template. Right now, this construct is unique to the ref-manual's chapter on the QA error and warnings chapter only. However, if for some reason that construct is used in any other part of the ref-manual, a generically numbered permalink would also be generated. The ref-manual-customization.xsl file was also altered to include the new documentation/template/qa-code-permalinks.xsl file. Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com> (From yocto-docs rev: aec27a9f8337575d31bfe0066563da99259046e0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed grammar use in "Image Features" list.Scott Rifenbark2014-10-101-1/+1
| | | | | | | (From yocto-docs rev: eb4ff8e1345987391e735f088d685ec70e641ed1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: remove bad patch snippet that eglibc forward portedSaul Wold2014-10-101-54/+0
| | | | | | | | | | | | | The s_sin.c patch undoes some code changes in glibc itself, these changes have nothing to do with the option groups and I suspect crept in as part of the initial conversion. Undoing this patch also fixes a test failure in test-double and test-idouble. [YOCTO #6808] (From OE-Core rev: 5f225067dcb7244065f857d34e1041171844b243) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchains-scripts: Add support for target environment scriptsRichard Purdie2014-10-101-0/+5
| | | | | | | | | | In a similar way to the previous script which adds support for native environment scripts, this adds support for target environment scripts too. (From OE-Core rev: 2d9466734f0c0c90724820bc36992b2800ffa4d0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk.py: fix write target sdk manifest failed based on ipkHongxu Jia2014-10-101-1/+1
| | | | | | | | | | | | | | | | | bitbake meta-toolchain ls tmp/deploy/sdk/poky-glibc-x86_64-meta-toolchain-i586-toolchain-1.7.manifest -al ... |-rw-rw-r-- 1 root root 0 Oct 10 15:05 tmp/deploy/sdk/poky-glibc-x86_64- meta-toolchain-i586-toolchain-1.7.manifest ... The manifest is empty, the reason is target's ipk config path is d.getVar('IPKGCONF_TARGET') rather than d.getVar('IPKGCONF_Target') (From OE-Core rev: 81b3cc448f040dcb4c2f2b05983231ac53270663) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wpa-supplicant: fix for rebuildRobert Yang2014-10-101-0/+2
| | | | | | | | | | | | | Fixed when rebuild: make: *** No rule to make target `/path/to/old//sysroots/qemux86-64/usr/lib/dbus-1.0/include/dbus/dbus-arch-deps.h', needed by `dbus/dbus_old.o'. Stop. The .d files save the path of the dependencies files which may not exist when rebuild, we can remove them to make the rebuild work. (From OE-Core rev: e336102e59dbbd01fe67121738203563476f9456) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: fix do_install errorRobert Yang2014-10-101-2/+5
| | | | | | | | | | | | | Fixed when MACHINE = qemux86-64 and libdir = /usr/lib64: mv: cannot stat `/path/to/image/usr/lib64/perl-native/perl': No such file or directory The perl-native files are always installed to /usr/lib on both 32/64 bits targets. (From OE-Core rev: fad6d25e548cb82c2106eb30ccdc0b8f3408de0a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi-ui: fix for building systemd with multilibRobert Yang2014-10-101-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed: MACHINE = "qemux86-64" VIRTUAL-RUNTIME_init_manager = " systemd " DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED += " sysvinit " require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake avahi avahi-ui ERROR: QA Issue: avahi-ui: Files/directories were installed but not shipped /lib /lib/systemd /lib/systemd/system /lib/systemd/system/avahi-daemon.socket /lib/systemd/system/avahi-dnsconfd.service /lib/systemd/system/avahi-daemon.service [installed-vs-shipped] ERROR: The recipe avahi-ui is trying to install files into a sharedarea when those files already exist. Those files and their manifestlocation are: /path/to/sysroots/qemux86-64/lib/systemd/system/avahi-daemon.socket Matched in manifest-qemux86-64-avahi.populate_sysroot /path/to/sysroots/qemux86-64/lib/systemd/system/avahi-dnsconfd.service Matched in manifest-qemux86-64-avahi.populate_sysroot /path/to/sysroots/qemux86-64/lib/systemd/system/avahi-daemon.service Matched in manifest-qemux86-64-avahi.populate_sysroot Please verify which recipe should provide theabove files. And remove the duplicated line: rm ${D}${base_libdir} -rf (From OE-Core rev: 1e6ec39d4996d2812b01c4452c579e476e70e85d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nss-myhostname: skip it when systemdRobert Yang2014-10-101-1/+4
| | | | | | | | | | | | | Fixed error when systemd is in DISTRO_FEATURES: ERROR: The recipe systemd is trying to install files into a sharedarea when those files already exist. Those files and their manifestlocation are: /path/to/sysroots/qemux86/usr/lib/libnss_myhostname.so.2 Matched in manifest-qemux86-nss-myhostname.populate_sysroot Please verify which recipe should provide theabove files. (From OE-Core rev: da70a62d456f7efac379381c2c431cc4ded877e9) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpcbind: make service socket activatedChen Qi2014-10-103-8/+14
| | | | | | | | | | Instead of setting 'Restart=always' in the service file, we should make the service socket activated, just like what Fedora does. (From OE-Core rev: 176e91ef28800adb6295b29c455b2efb91a01876) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: split the too long lineRobert Yang2014-10-101-1/+22
| | | | | | | | | | | | The too long line would cause "git send-email" report errors: patch contains a line longer than 998 characters Though we can use "--no-validate" to force the send. (From OE-Core rev: e96723879eb3352a5bdea7b3e1a576edf9550e5a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: the second bb.fatal not workRobert Yang2014-10-101-1/+1
| | | | | | | | | | | | | | The code: bb.fatal("foo1") bb.fatal("foo2") Would make the second one not work, use bb.error for first one to fix the problem. (From OE-Core rev: 33a87187a8520e190bcade76cc965aa58faaa85a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: Enforce 30 seconds limit for each testTudor Florea2014-10-101-15/+53
| | | | | | | | (From OE-Core rev: ae9a89fc1beac13f30395d191954fd70c3a9f85e) Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: fix build when ${PARALLEL_MAKE} contains '-l'Enrico Scholz2014-10-101-10/+18
| | | | | | | | | | | | | | The '-l' option which is valid for GNU make (--> limit by load) has a different meaning in bjam (--> limit maximum execution time) and will break very likely the build. Keep only the the '-l' option when passing PARALLEL_MAKE options to bjam. (From OE-Core rev: 1ff36aaec25a7ee89514366fe484345e8d1d7b64) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.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-13 06:56:48 +0000