summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* meta/selftest/scripts: Use print function for python3 compatibilityRichard Purdie2016-05-215-7/+7
| | | | | | | | | | | | Used print function instead of print statement to make the code work in python 3. [Changes from both Ed and Richard] (From OE-Core rev: ced1995694c394d92cb82fb9c25a33dc027a3b69) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: sdk-update: drop support for local updatesPaul Eggleton2016-05-211-3/+0
| | | | | | | | | | | | | Having two code paths here makes maintenance difficult, and it doesn't seem likely that you would use the local case in real usage anyway, so drop the local support entirely. This should allow us to resolve [YOCTO #9301]. (From OE-Core rev: 7a4c9c96fee4fb514c2b69b52e811c4f896a16f1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-glibc: Extend relocation support to localesRichard Purdie2016-05-211-32/+65
| | | | | | | | | | | | | | Currently locales are not found in a relocated buildtools-tarball such as that used in eSDK. This breaks bitbake when used under python3. This patch adds enough relocation magic to nativesdk-glibc so that the binary locales can be found even in a relocated buildtools-tarball and bitbake works successfully under python3. The eSDK also works correctly after this change too. (From OE-Core rev: faa1229ba848e7a4a90638a98d6c809065016a93) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc-locale: Enable binary locale generation for nativesdk-glibcRichard Purdie2016-05-211-1/+1
| | | | | | | | | | | | | python3 has much stricter locale requirements than previous versions. If a locale isn't present, python3 reverts to ascii mode under which bit bake can't operate. We therefore need working binary locales in things like uninative-tarball and buildtools-tarball. This patch enables binary locales for nativesdk-glibc. (From OE-Core rev: 6993d18062bcc20713dd39399bd7cb3623853c75) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: use 'lnr' instead of 'ln -sr'Ming Liu2016-05-211-2/+2
| | | | | | | | | For portability, not all hosts are running sufficiently new coreutils. (From OE-Core rev: b06d9ad6c235584f3cb12244bc5437ca7977a0c8) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: Upgrade to 2.7.3 releaseAndrew Bradford2016-05-211-2/+2
| | | | | | | | | | | | Linux 4.5 and later cause lttng-modules versions prior to 2.7.2 to fail to compile due to Linux vmscan changes. See lttng-modules git commit d0d2908478bdc8c36faaeae6fcb687052cb5f93b on lttng-modules branch stable-2.7: "Fix: update vmscan instrumentation for kernel 4.5". (From OE-Core rev: be62b6b78881a6a89242d99a258e1b26e7f13ee5) Signed-off-by: Andrew Bradford <andrew.bradford@kodakalaris.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkelfimage: obey LDFLAGS, sort out HOST_ flagsChristopher Larson2016-05-212-27/+62
| | | | | | | | | | | We weren't consistent in the HOST_ (aka BUILD_) and non-HOST_ flags, so we were using BUILD_CPPFLAGS to compile target stuff, for example. Sort that out, and make sure we obey LDFLAGS. (From OE-Core rev: 3ba4fd81f99b5479830d1fb18e6b8f2f6edb7839) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-weston: If X11 is enabled, add XWayland supportOtavio Salvador2016-05-211-0/+1
| | | | | | | | | | | When the distribution has X11 and Wayland backends, we enable XWayland support and include matchbox-terminal as a test application for the XWayland backend. (From OE-Core rev: f74cdf804ebe073137d5f126f7a0f31a39eb8b97) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Use weston-launch when starting weston as the first windowing ↵Tom Hochstein2016-05-211-1/+6
| | | | | | | | | | | | | | | system When weston is started as the first windowing system (i.e. not under X nor under another Wayland server), it should be done with the command weston-launch to set up proper privileged access to devices. (From OE-Core rev: 76ed534267ed16677eeb86b85670338a1064a733) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Add Xwayland initialization support using weston-startOtavio Salvador2016-05-212-1/+13
| | | | | | | | | | | The weston-start script now supports loading modules so the Xwayland support can be loaded optionally. Use this to load Weston accordingly. (From OE-Core rev: 4bbb5d5c0a4bed12622d06cd918ecd4d9db68b5e) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Add module support for the weston-start helperOtavio Salvador2016-05-212-0/+29
| | | | | | | | | | | | | | To make weston-start more flexible we now support module loading. For such modules, following functions can be used: - add_weston_argument - add_openvt_argument (From OE-Core rev: 3e7c4d06aaa1fccc1a18f4431122603cc4a9bbe9) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Error out if loading a nested instanceOtavio Salvador2016-05-211-0/+5
| | | | | | | | | | | | The Weston nested instance support is not implemented. This errors out displaying an informative error message so someone insterested on it may look at implement this later. (From OE-Core rev: 2332f93ae88ca4e4a5aac1806f21104b6489b3bb) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Rework init sequence to avoid code duplicationOtavio Salvador2016-05-214-13/+41
| | | | | | | | | | | The new 'weston-start' script redcues the code duplication for SysV and SystemD based images. (From OE-Core rev: 1963dfb002b9e0b4bff02dbf783909102ca59719) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Rework do_install to use install -D optionOtavio Salvador2016-05-211-5/+2
| | | | | | | | | | | | The install -D allow for the parent directories to be created in a single command line, reducing the code and number of fork during the build. (From OE-Core rev: 9d745d7c958402fa1d59c9d0267b58a05d7ee4b3) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Provide a default version of weston-launch that doesn't require PAMTom Hochstein2016-05-212-3/+177
| | | | | | | | | | | | | | | weston-launch requires PAM for starting weston as a non-root user. Since starting weston as root is a valid use case by itself, we check the distro for 'pam' and build weston-launch with or without non-root-user support. (From OE-Core rev: 6295197adc022445fff01ca5ee75780a4c007d99) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Remove XWayland dependencies on PACKAGECONFIGOtavio Salvador2016-05-211-2/+2
| | | | | | | | | | | | | | | Instead of adding partial dependencies we list the PACKAGECONFIG options that are required. Those are: X11 and Wayland. The previous value were redudant with X11 PACKAGECONFIG option and as it is a requirement, for XWayland, it can be removed to easy maintenance. (From OE-Core rev: f16f3d67fd71357de75e64e77414767629565e98) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Enable XWayland when X11 and Wayland support are availableOtavio Salvador2016-05-211-0/+5
| | | | | | | | | | | When the DISTRO has X11 and Wayland support enabled, XWayland ought to be enabled by default. (From OE-Core rev: b9a484b05e1901c5f612d23a006ee6f887ee2f17) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Add PACKAGECONFIG option for 'clients'Otavio Salvador2016-05-211-4/+3
| | | | | | | | | | This allow Weston to be build without the clients. (From OE-Core rev: a3084bd681f67b28b4e4b44ba0c6a281800f719d) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Fix SystemD service descriptionOtavio Salvador2016-05-211-1/+1
| | | | | | | | | | | | This improves the log shown in boot. Now it shows: [ OK ] Started Weston Wayland Compositor (From OE-Core rev: 32e9ef3089de6cf2da3a2b53579e5e015dfe6c12) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: weston-launch: Handle invalid command line optionsTom Hochstein2016-05-212-0/+34
| | | | | | | | | | | Exit the program if an unrecognized command line option is found. (From OE-Core rev: 9494ac03152174eee811e0534cf56e2248c58cc6) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/rootfs: Fix DEBUGFS generation, without opensslAnders Darander2016-05-201-0/+2
| | | | | | | | | | | | | | | | In commit 20ea6d274bb0a9a5addb111f32793de49b907865, debugfs generation for images using opkg, which included openssl was fixed. However, that broke the generation of the opkg-based images, that lacks openssl. The error is a python stack trace, showing that shutil.copytree tries to copy a non-existing directory. This relates to [YOCTO #9040]. (From OE-Core rev: f6b0b260ce18a30d04edfb0afb7942b9f9a5480b) Signed-off-by: Anders Darander <anders@chargestorm.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: Backport patch to changes with AVX and MPXbavery2016-05-202-1/+2602
| | | | | | | | | | | | | | | | | | | The current MPX target descriptions assume that MPX is always combined with AVX, however that's not correct. We can have machines with MPX and without AVX; or machines with AVX and without MPX. This patch adds new target descriptions for machines that support both MPX and AVX, as duplicates of the existing MPX descriptions. The following commit will remove AVX from the MPX-only descriptions. This commit is backported from 7.12 (From OE-Core rev: dee987b6f157b0bc245086d3af914d411ae6d1ab) Signed-off-by: bavery <brian.avery@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* acl.inc, run-ptest: improve ptest functionality on limited rootfsPeter Seebach2016-05-203-5/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | ACL's ptest has a handful of failure modes which can be triggered by a restrictive or small system. First, the ptest requires that daemon be in the bin group, which run-ptest attempts to do using gpasswd, but gpasswd is part of shadow, and oe-core removes shadow when it doesn't think shadow will be needed. Even if, say, a package has RDEPENDS on it. Whoops. So we manually sed the group file. This will probably work. Second, the filesystem used for the test has to support ACLs, so we create a dummy ext3 filesystem and use that. Third, the root/permissions test relies on the assumption that "mkdir d" produces a directory which non-root users can access, but in a secure product which defaults to umask 077, this doesn't work. (That fix has been separately reported to upstream acl through their bug report form.) (This may prevent the test from running without mkfs.ext3, but it allows the test to run on targets where root doesn't have ACL support. Tradeoffs, tradeoffs everywhere.) (From OE-Core rev: 0f1054e7db74bb4a196e00773915d7997b55bdf2) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: fix mesa_populate_packages() when dri is disabledHerve Jourdain2016-05-201-10/+11
| | | | | | | | | | | | | | | When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of DRI drivers is empty, it will cause populate_package to fail, because it can't find - rightfully - the directory for the DRI drivers. This patch checks that the directory indeed exists before trying to get a list of the files in it [ use oe.path.join instead of + - RB ] (From OE-Core rev: 7e96806d1282865761fcc047abcb72970279d82d) Signed-off-by: Herve Jourdain <herve.jourdain@neuf.fr> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/kernel: check OLDEST_KERNEL at configure timePaul Eggleton2016-05-201-0/+14
| | | | | | | | | | | | | | | | | If the kernel being built is older than OLDEST_KERNEL and we're building with glibc, then the C library we're building is probably not going to be compatible with the kernel and we should warn the user. (This is easier to do here rather than when building glibc, because we don't necessarily have the information we need to determine the kernel version there, whereas we do here.) Fixes [YOCTO #8653]. (From OE-Core rev: 2e66f57febe85a63ce2ab98eaf6318d47eb60939) 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>
* classes/kernel: fix typoPaul Eggleton2016-05-201-1/+1
| | | | | | | | | | KERNEL_VERISON -> KERNEL_VERSION (in a comment) (From OE-Core rev: 3f1d813e7183750b5189ae1ee99fd2f0bdeacac7) 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>
* bluez5: fixed path to bluetoothd in sysvinit scriptChristian Ege2016-05-202-1/+5
| | | | | | | | | | | Within the sysvinit script the path to bluetoothd is wrong. Because of this the init scripts silently terminates without any message (From OE-Core rev: 63cde9b8101ed39376529f3205d32729341d5802) Signed-off-by: Christian Ege <k4230r6@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Upgrade to 2.5.1.1 for fix CVE-2016-3710 and CVE-2016-3712Aníbal Limón2016-05-201-2/+2
| | | | | | | | | | | | | | This is a minor upgrade only comes with security fixes in qemu VGA and UART code to avoid corruptions. For review details, http://git.qemu.org/?p=qemu.git;a=log;h=v2.5.1.1 (From OE-Core rev: da522c0c248c9a8b10a90de4cd6e7e05367e637d) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: update homepage and summaryStephano Cetola2016-05-201-2/+3
| | | | | | | | | | | | | The homepage variable is out of date and the summary does not mention ssh, making the recipe difficult to find. [ YOCTO #9610 ] (From OE-Core rev: ce84dc09172b98ce1162e536db17148a67ba2be1) Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: adjust variable blacklistingPaul Eggleton2016-05-201-0/+4
| | | | | | | | | | | | | | | * Blacklist SSTATE_DIR, DL_DIR and TMPDIR by default to avoid problems such as the one mentioned in [YOCTO #9605]. * Blacklist BB_NUMBER_PARSE_THREADS since we already blacklist BB_NUMBER_THREADS and they may be set separately. Fixes [YOCTO #9605]. (From OE-Core rev: 3f2dcaaab0f5bc169086a8b6fd57c5606742cc4d) 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>
* linux-dummy: set INHIBIT_DEFAULT_DEPSRobert Yang2016-05-201-0/+2
| | | | | | | | | | It doesn't need them. (From OE-Core rev: dc7036e8bcddb1d29739ebd4c75b150283a10ec0) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: fitimage: Repair misuse of shell test commandMarek Vasut2016-05-201-1/+1
| | | | | | | | | | | | | | | | | The kernel fitImage must be amended with signature if and only if UBOOT_SIGN_ENABLE = 1 . In the current case, the UBOOT_SIGN_ENABLE could be either 0 (default) or 1 , which test -n always correctly interprets as non-empty string, thus always true. This does not match the logic above though, so replace the test with check which passes only for UBOOT_SIGN_ENABLE = 1 . (From OE-Core rev: 158cbd737f9f6c2de756506caf919a0a3d0a05b9) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Yannick Gicquel <yannick.gicquel@iot.bzh> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: move btmgmt to common READLINE sectionNicolas Dechesne2016-05-201-1/+1
| | | | | | | | | | | | Upstream in 5.33 btmgmt was moved from experimental to common READLINE section, in commit e4f0c5582f1fe3451d5588243adba9de1ed68b80, but this was never updated in the recipe. (From OE-Core rev: 28777e593d3dd3a5d0ee2effcdca6a971e2887f9) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: turn off JIT on armv4 and armv7aRobert Yang2016-05-201-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | * It doesn't build on armv4: {standard input}: Assembler messages: {standard input}:52: Error: selected processor does not support `blx llint_throw_stack_overflow_error' in ARM mode {standard input}:126: Error: selected processor does not support `bkpt #0' in ARM mode {standard input}:128: Error: selected processor does not support `blx r0' in ARM mode {standard input}:134: Error: selected processor does not support `bkpt #0' in ARM mode {standard input}:185: Error: selected processor does not support `blx llint_throw_stack_overflow_error' in ARM mode {standard input}:256: Error: selected processor does not support `blx r4' in ARM mode {standard input}:310: Error: selected processor does not support `movw r2,#:lower16:.Lllint_op_enter-.LrelativePCBase' in ARM mode {standard input}:311: Error: selected processor does not support `movt r2,#:upper16:.Lllint_op_enter-.LrelativePCBase' in ARM mode {standard input}:315: Error: selected processor does not support `movw r2,#:lower16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode {standard input}:316: Error: selected processor does not support `movt r2,#:upper16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode [snip] * It can build on armv7a, but doesn't work on runtime, cause displaying problems or ephiphany hang. [YOCTO #9474] (From OE-Core rev: 8d397781665ac71615e9e0a240a76272b6b63216) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa-demos: provide option for disabling GLX demosAwais Belal2016-05-202-1/+65
| | | | | | | | | | | | There are platforms that default to EGL only configurations in which case the GLX applications are not required at all. Allow the user to control generation of these demos as needed through a configure switch. (From OE-Core rev: 226492af41234dec47066d576d0de78fd09a4ca8) Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: moves KERNEL_SRC_PATH to bitbake.confMing Liu2016-05-194-8/+5
| | | | | | | | | | "/usr/src/kernel" is being hard-coded in multiple recipes so far, move its definition to bitbake.conf. (From OE-Core rev: eb9f900527e02ca08a1de14b4ac773f513bb1ee4) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* zip: update SRC_URIRoss Burton2016-05-192-35/+32
| | | | | | | | | | | | | | | The infozip FTP server appears to have been taken down, so change the SRC_URI to point at their SourceForge project. Also as the SRC_URI can't be generated from the version and there is no other user of the .inc, merge the .bb and .inc together. [ YOCTO #9655 ] (From OE-Core rev: 5cb1e0ec46e4fde1c15aeb6812eaaece4840ac1c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unzip: update SRC_URIRoss Burton2016-05-191-1/+1
| | | | | | | | | | | | The infozip FTP server appears to have been taken down, so change the SRC_URI to point at their SourceForge project. [ YOCTO #9655 ] (From OE-Core rev: 879b2c5ee2ae39d6c1ae9d44ab243d8c7b7874b4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgudev: fix upstream checkMaxin B. John2016-05-191-0/+2
| | | | | | | | | | Provide UPSTREAM_CHECK_URI and UPSTREAM_CHECK_REGEX to fix upstream check. (From OE-Core rev: 3e882977f9185161a9ec0e6fe9aeae1a445252f8) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* freetype: fix upstream checkMaxin B. John2016-05-191-0/+3
| | | | | | | | | | Provide UPSTREAM_CHECK_URI and UPSTREAM_CHECK_REGEX for proper upstream check. (From OE-Core rev: a80a084fc077ee47c279e900d0a9c531c4ee52d8) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: remove deprecated fileMaxin B. John2016-05-192-23/+0
| | | | | | | | | | Remove this file as it has been deprecated in the previous release. New entries should be added to recipes itself. (From OE-Core rev: a3075bf29f0fa80489e3dd2ade65cc3a3b3d0332) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Update to 1.1 tarball (new version of glibc)Richard Purdie2016-05-191-3/+3
| | | | | | | | | Since we have a new version of glibc, upgrade to a new version of the uninative tarball to ensure we work on recent distributions. (From OE-Core rev: 15476fae90efe7765159b342916e536a2f6e8fc1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Unify _log_check_warn() and _log_check_error()Peter Kjellerstedt2016-05-191-38/+14
| | | | | | | | | | | | | | | | | | | Use a common _log_check_common() function (based on the old _log_check_warn() function) to implement the logic for both _log_check_warn() and _log_check_error(). The main benefit of this is that now all error messages will be reported again, not just the first one found. Additionally the output will now look the same for both error and warning messages. This removes the context for the error messages. However, since there was no indication in the output that some of the lines were context, they were more confusing than helping. (From OE-Core rev: dd73dcac36b80b3b886a2e9bf575b91c4f60d039) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Reduce spam from _log_check_warn()Peter Kjellerstedt2016-05-191-2/+9
| | | | | | | | | | | | | | | | For each warning found in the log, _log_check_warn() would output a line stating that it had found a warning, then the actual warning and finally an empty line. This is quite excessive when there are many warnings in the log. With this change the output is instead a line stating how many warnings were found, followed by the warnings. This makes the output much more compact and actually much more readable. (From OE-Core rev: d6e3477749b1d09d40a773e0ac857a24d5851984) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Exclude lines in _log_check_warn() as wellPeter Kjellerstedt2016-05-191-4/+15
| | | | | | | | | | This will make _log_check_warn() exclude the same lines as _log_check_error() does. (From OE-Core rev: 85f64c68278f797c6f73f002f63d7f46fe80aef4) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Use one way to exclude lines in _log_check_error()Peter Kjellerstedt2016-05-191-13/+12
| | | | | | | | | | | | Before there were three different ways to exclude a line from being searched for error messages in _log_check_error(). Now there is only one: an array of regular expressions. This should make it easy to add more excludes if nedded. (From OE-Core rev: 321df88088fbfa657b61b2bae32751f03daec46f) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Simplify the regular expression used in _log_check_warn()Peter Kjellerstedt2016-05-191-2/+2
| | | | | | | | | | | | In commit 0387d095 lines with "NOTE:" in them were excluded from the log check for warnings. However, those lines were only there in the first place since the regular expression that is used to find warning messages explicitly included those lines... (From OE-Core rev: 865ab39f18a52ed84217df56d0e65113e2894d02) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Remove _log_check_error() from the RpmRootfs classPeter Kjellerstedt2016-05-191-26/+3
| | | | | | | | | | | | | | | | | | | | | The fact that this function was overridden in the RpmRootfs class seems to have led to a number of misstakes when changes have been made to the base function in the Rootfs class. E.g., this change will properly solve ticket 7789, which was supposedly solved in 38871dc0, but that change had no effect in practice as the log_check_regex that was modified for RpmRootfs class was not used by the RpmRootfs version of _log_check_error()... The only thing _log_check_error() in RpmRootfs did that the base function in Rootfs did not do was to skip lines in the log that begin with a + sign. This has now been moved to the base function instead. [YOCTO #7789] (From OE-Core rev: 1eb0a46502fca4b2ee30ccd2508f4e21a40c25ca) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "rootfs.py: add more info to the warning message"Peter Kjellerstedt2016-05-191-1/+0
| | | | | | | | | | | | | | | | | The reverted commit added a warning with the log line that triggered the log check for error messages before the warning that states that an error has been found in the log. However, the error line is output by the call to bb.fatal() that follows immediately after the original warning, which makes it redundant. Additionaly, having two warnings contradicts the intent of commit 8dfdd329 where the log warnings were tidied up. This reverts commit f9cf31525fc885e1a0f65bd55654631257f87078. (From OE-Core rev: e509a83c8eb5a572aad7e7451d019fa2469d70c3) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysprof: Disable nios2 supportMarek Vasut2016-05-191-1/+2
| | | | | | | | | | | | | | sysprof does not support nios2 yet, so disable it. (From OE-Core rev: ba6b3674e7788dd3a8aa0a2c830fa78badf68532) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Ley Foon Tan <lftan@altera.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Cc: Thomas Chou <thomas@wytron.com.tw> Cc: Walter Goossens <waltergoossens@home.nl> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-18 00:42:24 +0000