Dengke Du [Tue, 23 Feb 2016 06:03:38 +0000 (01:03 -0500)]
pTest-strace fails fixed
When run the strace ptest on the target, the test files located in the "/usr/lib/strace/ptest/tests",
but the run-test script use the path "srcdir = ../../strace-*/tests"to find the necessary files, so it
can't find the necessary files, it fails. So change the variable srcdir, replace the strace-* to ptest
when do the do_install_ptest() function using the following:
sed -i -e '/^src/s/strace.*[1-9]/ptest/' ${D}/${PTEST_PATH}/${TESTDIR}/Makefile
Signed-off-by: Dengke Du <dengke.du@windriver.com>
Richard Purdie [Tue, 2 Feb 2016 23:55:37 +0000 (23:55 +0000)]
bitbake: data_smart: Drop default expand=False to getVarFlag [API change]
At some point in the future, getVarFlag should expand by default. To
get there from the current position, we need a period of time where the
expand parameter is mandatory.
This patch starts that process. Clear errors will result from any code
which doesn't provide this. Layers can be fixed with an expression
like:
sed -e 's:\(\.getVarFlag([^,()]*, [^,()]*\)):\1, False):g' -i `grep -ril getVar *`
Richard Purdie [Tue, 2 Feb 2016 23:55:40 +0000 (23:55 +0000)]
bitbake: data_smart: Drop default expand=False to getVar [API change]
At some point in the future, getVar should expand by default. To get
there from the current position, we need a period of time where the
expand parameter is mandatory.
This patch starts that process. Clear errors will result from any code
which doesn't provide this. Layers can be fixed with an expression
like:
sed -e 's:\(\.getVar([^,()]*\)):\1, False):g' -i `grep -ril getVar *`
Markus Lehtonen [Tue, 26 Jan 2016 13:34:29 +0000 (15:34 +0200)]
bitbake: bb/runqueue: save task file dependency cache onto disk
Before this patch the usage of cache was quite useless as the file
checksums were not actually cached on disk but re-calculated every time.
This patch utilises the new writeout_file_checksum_cache() method of the
SignatureGenerator class to do the job.
Markus Lehtonen [Tue, 26 Jan 2016 13:34:28 +0000 (15:34 +0200)]
bitbake: SignatureGenerator: add method for saving the file checksum cache
Extend the API in order to be able to write out the file checksum cache
onto disk. SignatureGeneratorBasic class now implements a method that
update the fetcher local files checksum cache with the task file
dependency checksums.
Mirela Rabulea [Tue, 19 Jan 2016 14:31:38 +0000 (16:31 +0200)]
bitbake: Allow Hob to run images on a custom simulator, other than qemu
The current behavior of Hob is that there is a "Run Image" button which becomes visible only for qemu images.
My suggested change is:
- if an image is selected and it is qemu-compatible, let the "Run image" button be named "Run qemu image"
- if an image is selected and it is not qemu-compatible, let the same button show up with the name "Run custom image", and besides that, an option shows-up to allow the selection of the custom script (by default it points out to runqemu script) to be used for launching this custom image
Note: in case there is more than one toggled image (qemu runnable or deployable), when the user clicks the "Run custom image" button, a dialog will be presented, allowing to choose between any of the existing images.
gma500-gfx-check: Fixes infinite calling to modprobe gma500_gfx
The previous script caused an infinite call to modprobe gma500_gfx on certain
situations, this fixes a typo and uses a new flag to avoid the infinite loop
Tanu Kaskinen [Wed, 17 Feb 2016 16:56:16 +0000 (18:56 +0200)]
pulseaudio: 6.0 -> 8.0
Release notes for 7.0:
https://wiki.freedesktop.org/www/Software/PulseAudio/Notes/7.0/
Release notes for 8.0:
https://wiki.freedesktop.org/www/Software/PulseAudio/Notes/8.0/
7.0 added support for soxr resamplers, but neither oe-core nor meta-oe
have libsoxr packaged. The default resampler is still speexdsp based,
so most people wouldn't be using the soxr resamplers anyway. If
someone cares enough to package soxr, then we can enable the feature.
Bash completions moved in 7.0 from /etc to the standard location under
/usr/share/bash-completion. We now use the bash-completion class to
package the completion files.
The private library libpulsecore moved from /usr/lib to
/usr/lib/pulseaudio.
The new routing features advertised in the 8.0 release notes are
reverted for now, because they caused regressions. I'll remove the
revert once a proper fix is available.
Removed two patches, because they are included in the new release.
Rebased three patches.
Updated Upstream-Status tags to reflect the current situation.
The licensing of the libsamplerate plugin was relaxed a bit: if the
licensee has a commercial license for libsamplerate, the plugin can be
used under the terms of LGPL instead of GPL.
Both old patches are included in the new release, so dropped them.
Added a new patch to fix building against libspeexdsp 1.2rc3.
This release introduces two new tools:
- alsatplg for converting topology data from text representation to a
binary format consumed by the kernel
- alsabat; "bat" stands for "basic audio tester"
Backported a patch from upstream that renames bat to alsabat.
Dropped patches "alsa-utils-aplay-interrupt-signal-handling.patch" and
"assume-storing-is-success-if-not-sound-card-device.patch", because
the issues have been fixed upstream.
Maxin B. John [Wed, 17 Feb 2016 14:00:19 +0000 (16:00 +0200)]
avahi: update to version 0.6.32
0.6.31 -> 0.6.32
a. Switched to the new repository hosted in github.
b. Removed the following Upstreamed/Backported patches
1. 0001-Don-t-log-warnings-about-invalid-packets-Fixes-lathi.patch
2. 0001-avahi-fix-avahi-status-command-error-prompt.patch
3. avahi_fix_install_issue.patch
4. fix_for_automake_1.12.x.patch
5. out-of-tree.patch
6. reuseport-check.patch
c. Added UPSTREAM_CHECK_URI
Richard Purdie [Wed, 17 Feb 2016 13:33:40 +0000 (13:33 +0000)]
libsdl2: Fix build with static libraries disabled
libsdl2 was using foo.o in Makefile dependencies but if libtool is
being used then those are the statically linked intermediate files.
When static libraries are globally disabled they won't be generated by
libtool so the build fails.
Instead, use the libtool intermediate wrapper .lo files so the build
succeeds.
Erkka Kääriä [Wed, 17 Feb 2016 11:54:34 +0000 (13:54 +0200)]
uboot-inc: Backport patch to fix Beaglebone Black bootloader
Beaglebone Black boot started failing after upstream patch 755324c432f, and was
fixed in 7205442e6. Unfortunately, the u-boot upgrade from 2015.10 to 2016.01
only includes the former patch. The latter patch is backported to fix this.
Maxin B. John [Wed, 17 Feb 2016 11:01:11 +0000 (13:01 +0200)]
busybox: drop patches that are not valid anymore
1. Removed following patches
a) busybox-appletlib-dependency.patch
- Kbuild rules handles that dependency
b) get_header_tar.patch
- tar applet uses a different code path to handle that scenario now.
2. Updated the upstream-status of fail_on_no_media.patch as Denied.
Ulrich Ölmann [Wed, 17 Feb 2016 09:30:36 +0000 (10:30 +0100)]
nfs-utils: bugfix: adjust name of statd service unit
Upstream nfs-utils use 'rpc-statd.service' and Yocto introduced
'nfs-statd.service' instead but forgot to update the mount.nfs helper
'start-statd' accordingly.
Khem Raj [Wed, 17 Feb 2016 08:45:15 +0000 (08:45 +0000)]
musl: Upgrade to 1.1.13+
Rich Felker (3):
fix assumption in fputs that fwrite returning 0 implies an error
fix unlikely corner cases in getopt's message printing
in crypt-sha*, reject excessive rounds as error rather than clamping
Signed-off-by: Marek Vasut <marex@denx.de> Cc: Alexander Kanavin <alexander.kanavin@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Tue, 16 Feb 2016 20:56:08 +0000 (20:56 +0000)]
glew: rewrite to use upstream build system
Instead of patching in a whole new build system using autotools, use the
makefile-based system in upstream with careful variable assignments so that it
cross-compiles correctly. One small patch was required to stop an unavoidable
strip.
Upstream does have a cmake-based build but it's not used or supported by the
maintainer, and is quite buggy (for example: doesn't version the libraries,
fails to link to required libraries).
Khem Raj [Tue, 16 Feb 2016 21:14:09 +0000 (21:14 +0000)]
binutils: Fix useless rpaths QA warning
elfedit and readelf contains /usr/lib in elf header
this patch deletes them from binaries, ideally it
should be fixed in libtool and Makery of binutils
mips target binutils dont build gold so remove
them from ALTERNATIVES list
depend on own version of chrpath native, so builds on
build OS like Centos can work, the verison of chrpath
on centos is old enough to not support dealing with
multi-arch ELF files.
Chen Qi [Wed, 17 Feb 2016 05:21:22 +0000 (13:21 +0800)]
image/populate_sdk: seprate variables to fix dependency
Previously, do_rootfs depends on variables like SDK_OS, SDK_OUTPUT, etc.
And changing variables like POPULATE_SDK_POST_HOST_COMMAND doesn't cause
do_populate_sdk to rerun.
This patch separates variables so that do_rootfs and do_populate_sdk could
correctly depend on their related variables.
Marek Vasut [Wed, 17 Feb 2016 00:29:36 +0000 (01:29 +0100)]
gcc: Backport nios2 r31 fix
Backport a fix from GCC mainline, which fixes libpcre 8.38 and expat 2.1.0
build on nios2. The example of the fixed error follows:
| ./nios2-poky-linux-libtool --silent --mode=compile nios2-poky-linux-gcc -mel -mhw-div -mhw-mul --sysroot=/mnt/work/Yocto/build-nios2/tmp/sysroots/10m50 -I../expat-2.1.0/lib -I. -O2 -pipe -g -feliminate-unused-debug-types -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o lib/xmltok.lo -c ../expat-2.1.0/lib/xmltok.c
| {standard input}: Assembler messages:
| {standard input}:4988: Error: r31 cannot be used with jmp; use ret instead
| {standard input}:9703: Error: r31 cannot be used with jmp; use ret instead
| {standard input}:20068: Error: r31 cannot be used with jmp; use ret instead
| {standard input}:24020: Error: r31 cannot be used with jmp; use ret instead
| Makefile:196: recipe for target 'lib/xmltok.lo' failed
| make: *** [lib/xmltok.lo] Error 1
| WARNING: exit code 1 from a shell command.
Ross Burton [Tue, 16 Feb 2016 16:27:19 +0000 (16:27 +0000)]
cmake: don't inherit autotools
autotools was inherited for some functions some time ago, but now all it's using
it for explicitly is autotools_do_install(), which is basically just "make
install". Invoke that directly and we can remove the inherit autotools.
Hongxu Jia [Tue, 16 Feb 2016 09:14:55 +0000 (04:14 -0500)]
bitbake.conf: use target path as compile dir in debugging info
In debugging information, it uses target paths rather than
build ones as compile dir.
...
-fdebug-prefix-map=old=new
When compiling files in directory old, record debugging
information describing them as in new instead.
...
Compile without this fix:
objdump -g git/test.o
...
The Directory Table (offset 0x1b):
| 1 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/x86_64-linux/usr/lib/
i686-pokymllib32-linux.lib32-gcc-cross-initial-i686/gcc/i686-pokymllib32-linux/5.3.0/include
| 2 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/lib32-qemux86-64/usr/include/bits
| 3 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/lib32-qemux86-64/usr/include
...
Compile with this fix:
objdump -g git/test.o
...
The Directory Table (offset 0x1b):
| 1 /usr/lib/i686-pokymllib32-linux.lib32-gcc-cross-initial-i686/gcc/i686-pokymllib32-linux/
5.3.0/include
| 2 /usr/include/bits
| 3 /usr/include
...
Armin Kuster [Sat, 23 Jan 2016 04:25:19 +0000 (20:25 -0800)]
glibc: CVE-2015-8776
it was found that out-of-range time values passed to the strftime function may
cause it to crash, leading to a denial of service, or potentially disclosure
information.
Armin Kuster [Sat, 23 Jan 2016 04:23:04 +0000 (20:23 -0800)]
glibc: CVE-2015-9761
A stack overflow vulnerability was found in nan* functions that could cause
applications which process long strings with the nan function to crash or,
potentially, execute arbitrary code.
Armin Kuster [Sat, 23 Jan 2016 04:19:24 +0000 (20:19 -0800)]
glibc: CVE-2015-8779
A stack overflow vulnerability in the catopen function was found, causing
applications which pass long strings to the catopen function to crash or,
potentially execute arbitrary code.
Armin Kuster [Sat, 23 Jan 2016 04:13:00 +0000 (20:13 -0800)]
glibc: CVE-2015-8777.patch
The process_envvars function in elf/rtld.c in the GNU C Library (aka glibc or
libc6) before 2.23 allows local users to bypass a pointer-guarding protection
mechanism via a zero value of the LD_POINTER_GUARD environment variable.
Richard Purdie [Tue, 16 Feb 2016 23:49:52 +0000 (23:49 +0000)]
rng-tools: Fix underquoted m4 and libgcrypt floating dependency
The underquoted m4 caused build failures if libgcrypt wasn't present. The floating
dependency on libgcrypt was just plain incorrect, particularly given the incorrect
libgcrypt RDEPENDS. Change to use PACKAGECONFIG an default to on.
Ross Burton [Mon, 15 Feb 2016 17:48:25 +0000 (17:48 +0000)]
lib/qa.py: raise ValueError if file isn't an ELF
Instead of raising a generic Exception that can't be handled specifically, raise
a ValueError. Also update the callers so any unexpected exceptions are not
ignored.
Ross Burton [Mon, 8 Feb 2016 20:35:40 +0000 (20:35 +0000)]
lib/oe/qa: ELFFile: check that a path is a file before opening it
When opening an ELF file check that a filename points to a normal file before
attempting to open it, as if the file turns out to be something more exotic like
a FIFO it could hang forever.
musl doesn't provide argp, so we need argp-standalone, as we do for uclibc.
Rather than passing in -largp via the recipe, patch the configure script to
provide an argument for the libargp usage and check for it when needed, and
use PACKAGECONFIG. The initial patch to check for libargp and use it if
available came from Gentoo. The patches are kept separate despite the second
modifying what the first does, in order to keep the history/origin clear.
Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Markus Lehtonen [Mon, 15 Feb 2016 15:01:49 +0000 (17:01 +0200)]
nss: define RPATH variable for nss-native
Otherwise the nss libs do not get any RPATH/RUNPATH. Consequently, the
.so dependencies of nss libs are always searched from the base lib
directories of the host (i.e. /lib/ and /usr/lib). This causes problems
with nss-native where the .so's should be searched from the base lib
directories of the sysroot instead of the host file system.
This particular problem has probably been unnoticed as most users are
likely to have nss libraries installed on their host system. In this
case everything most likely work as expected.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
util-linux upstream, busybox, and sysvinit all install mountpoint by
default to /bin. Arch Linux, Debian, and Ubuntu (at least) all appear to
install mountpount to /bin. AFAIK only Fedora and possibly other Red Hat
derived distributions install it to /usr/bin.
Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Reviewed-by: Ken Sharp <ken.sharp@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Mon, 15 Feb 2016 09:47:33 +0000 (09:47 +0000)]
libunwind: Fix build on ppc
gcc driver is fixed to pass correct options to linker to do secure plt
linking when enabled. however this option --secure-plt is not supported
by gold linker which is now passed by default from gcc driver. Hence
the build fails when using gold. Therefore when we use gold then we do
not use secure plt
Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runtime/systemd: Fix for boot time string parse error
boot time string can change its format of the output of the amount of time
it took to boot. It is required to handle graceful fail of the parsing
errors that it provokes
this causes linking errors when linking libbfd.so since objects (.o) are
compiled using -fstack-protector-strong so they are expecting to link
with libssp but the option goes missing in linker flags.
With this patch the security flags are hoisted upto CC itself and
libtool thankfully does not touch CC.
Adding to CC also means that we can now remove it from LDFLAGS since
when gcc driver is used to do linking then we have LD = CC and this
option makes to linker cmdline
Since CC is used without CFLAGS in configure tests, some tests fail
complaining that -Olevel is not used while using _FORTIFY_SOURCE
therefore added SELECTED_OPTIMIZATION to TARGET_CC_ARCH as well
Khem Raj [Sun, 14 Feb 2016 20:52:51 +0000 (20:52 +0000)]
binutils: Use tip of 2.26 branch
Until 2.26.1 is released there are few fixes which are needed especially
when using -fpie, here are changes that are part of this version bump
H.J. Lu (7):
Add a testcase for PR ld/18591
Store estimated distances in compressed_size
Remove duplicated marker for 2.26 in gas/NEWS
Add -mrelax-relocations= to x86 assembler
Mask off the least significant bit in GOT offset
Enable -Bsymbolic and -Bsymbolic-functions to PIE
Fix a typo in objcopy manual
John David Anglin (1):
Fix /usr/bin/ld: final link failed: File truncated error on hppa
Patrick Ohly [Fri, 12 Feb 2016 08:37:15 +0000 (09:37 +0100)]
buildhistory.bbclass: remove out-dated information on request
buildhistory.bbclass by design is incremental: each build adds or
updates information. Information is never removed.
Sometimes it can be useful to reduce the information only to those
recipes that were build during a specific bitbake invocation, for
example when the invocation does a full world build.
This is now possible by setting BUILDHISTORY_RESET as explained in the
modified class. The comment on the variable also mentions the caveats
associated with using this mode.
In this mode, buildhistory.bbclass first moves all existing
information into a temporary directory called "old" inside the build
history directory. There the information is used for the "version
going backwards" QA check. Then when the build is complete and before
(potentially) committing to git, the temporary directory gets deleted.
Because information that has not changed during the build will be
reconstructed during full world rebuilds, a git log will then only
show real updates, additions and removals.
Randy MacLeod [Tue, 9 Feb 2016 02:46:50 +0000 (21:46 -0500)]
Remove obsolete references to exmap
Exmap was a useful tool but it appears to be unsupported.
Remove it from the sample local.conf and remove the
commented lines from the profile tools packagegroup.
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sun, 14 Feb 2016 23:09:49 +0000 (23:09 +0000)]
bitbake: knotty: Set exit failure code on runQueueTaskFailed events
If the worker segfaults, we may never see a TaskFailed event from it, only
a runQueueTaskFailed event. In this case, return_value isn't getting set
leading to an incorrect exit code from bitbake. Fix by setting return_value
in both places.
Richard Purdie [Sun, 14 Feb 2016 10:14:22 +0000 (10:14 +0000)]
bitbake: taskdata: Fix traceback issue with missing provider
If there is a missing provider and we're using "-k" mode alongside "-w",
we could get a traceback since there was no provider. Add tests to avoid this.
Richard Purdie [Sun, 14 Feb 2016 09:11:24 +0000 (09:11 +0000)]
bitbake: cooker: Improve cache handling
We're seeing issues where the self test, which uses tinfoil doesn't
notice the changed contents of include files. The issue is
cached_statements in the parser being reused when the files have changed.
Whilst looking at this, I realised there were some other issues:
* We need to also invalidate the mtime cache when cooker restarts
* We should pass full filenames to the file invalidation code
* We should process cached_statements as part of inotify invalidation
With these fixes, the caching is more reliable for memory resident
bitbake too. It does raise some questions about cache validation and
lifecycles and indicates bitbake does need more work in the area,
preferably with the removal of the globals. This at least highlights
and works around some of the current issues.
Richard Purdie [Sun, 14 Feb 2016 14:32:13 +0000 (14:32 +0000)]
poky: Disable static libs by default
Static libraries are old technology. We've left them around since in
previous tests, they only added around 5% to the overall build time.
With new and interesting uses of OE, they're becoming more problematic.
For example, sstate becomes much larger with static libs enabled which
increases the size of eSDK and increases the time taken for sstate
operations. Since the static libs contain all the debugging symbols,
they're also pretty huge.
Therefore use the common include which enables this from OE-Core.
Mike Crowe [Tue, 2 Feb 2016 14:49:47 +0000 (14:49 +0000)]
bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKE
Setting EXTRA_OEMAKE to "-e MAKEFLAGS=" by default is a historical
accident and many classes (e.g. autotools.bbclass, module.bbclass) and
recipes have to override this default in order to work with sensible
build systems.
Now that openssl and pciutils have been fixed to set EXTRA_OEMAKE
explicitly it is possible to set EXTRA_OEMAKE = "".
Ross Burton [Mon, 15 Feb 2016 15:56:33 +0000 (15:56 +0000)]
apmd: fix build with static libraries disabled
apmd was using foo.o in Makefile dependencies but if libtool is being used then
those are the statically linked intermediate files. When static libraries are
globally disabled they won't be generated by libtool-cross so the build fails.
Instead, use the libtool intermediate wrapper .lo files so the build succeeds.
Richard Purdie [Sun, 14 Feb 2016 14:28:48 +0000 (14:28 +0000)]
conf/distro/include: Add no-static-libs.inc
Static libraries are old technology. We've left them around since in
previous tests, they only added around 5% to the overall build time.
With new and interesting uses of OE, they're becoming more problematic.
For example, sstate becomes much larger with static libs enabled which
increases the size of eSDK and increases the time taken for sstate
operations. Since the static libs contain all the debugging symbols,
they're also pretty huge.
This patch adds a common include file which allows the user or distro
to disable the static libraries in the majority of cases.
There are some libs where we do need the static lib, a good example
being pseudo-native which uses sqlite3-native static libs. These are
left enabled by the include file, as are recipes where --disable-static
doesn't work, or isn't supported. This list can likely be reduced over
time as individual corner cases are addressed.
Maintaining this list in a common location is more desireable than
everyone doing it themselves. Poky will switch to using this, OE-Core
will need to discuss that as its default.
Paul Eggleton [Sun, 14 Feb 2016 20:13:03 +0000 (09:13 +1300)]
classes/buildhistory: fix for python function parsing change
Variable expressions are no longer expanded in python functions as of
BitBake commit 8bf33a8e92c0e188fa392030025756196c96fcbb, so we've now
got to do this explicitly here.
Richard Purdie [Sun, 14 Feb 2016 23:03:33 +0000 (23:03 +0000)]
gstreamer1.0-meta-base: Mark as machine specific due to COMBINED_FEATURES
http://git.openembedded.org/openembedded-core/commit/?id=948165dce7475b815a344fd3c3d58165e6865d48
makes gstreamer1.0-plugins-base-alsa depend on COMBINED_FEATURES.
This is an allarch recipe so this only works if all your machines
have the same MACHINE_FEATURES.
The recipe therefore needs to become machine specific.
Richard Purdie [Sun, 14 Feb 2016 14:30:40 +0000 (14:30 +0000)]
insane: Add --disable-static to UNKNOWN_CONFIGURE_WHITELIST
With the addition of a common class passing in this option, add it to
the list of standard "unknown" configure options which are known about.
Its not interesting/productive to go and update every recipe to handle
this flag.
Richard Purdie [Sun, 14 Feb 2016 09:25:34 +0000 (09:25 +0000)]
linux-yocto: Work around PAT issue on qemux86
We have an issue with PAT handling on older processes with limited PAT bits,
see the patch description for the full problem. This replaces the runqemu
workaround with a kernel patch until we can get the kernel trees sorted
out and discuss a proper fix with upstream. It should be safe everywhere
so is applied unconditionally.
Andre McCurdy [Sat, 13 Feb 2016 01:04:10 +0000 (17:04 -0800)]
musl: Upgrade to tip of tree
Includes misc minor bugs fixes:
0ed932f do not define static_assert macro for pre-C11 compilers 692b16d add declarations for utmpname/utmpxname to appropriate headers 500c688 fix return value for fread/fwrite when size argument is 0 416d1c7 fix line-buffered flush omission for odd usage of putc-family functions 5a6e8d0 fix failed write reporting by fwrite in line-buffered mode 869a9df remove workaround for broken mips assemblers
The addition of utmpname/utmpxname prototypes fixes a change
introduced in the previous git snapshot version which broke lxc.
Ed Bartosh [Sat, 13 Feb 2016 09:02:21 +0000 (11:02 +0200)]
oe-selftest: don't use specific tasks
Image should be build usual way, i.e. using bitbake <image>.
Specifying do_mage_complete and do_rootfs_wicenv tasks should not
be needed anymore as those tasks should be run by bitbake for
every image.
Removed specifying do_mage_complete and do_rootfs_wicenv tasks
from bitbake calls.
Ed Bartosh [Sat, 13 Feb 2016 09:02:19 +0000 (11:02 +0200)]
wic-image-minimal: use uuid for root partition
Used --uuid option to generate PARTUUID for root partion and
gpt partition type. As this image is used in runtime testing
under qemu it makes sense to ensure that this way of specifying
root partition works.
Added dependency to gptfdisk-native to wic-image-minimal recipe to
be able to create gpt partition table.
Ed Bartosh [Sat, 13 Feb 2016 09:02:18 +0000 (11:02 +0200)]
wic: fix processing of --use-uuid
Processing of this option was lost during recent change of
wks parsting. It was discovered during the work on booting
wic images under qemu. Now, when -use-uuid is fixed it's
possible to specify root partition by partition uuid.
This will be done in the following commit.
Ed Bartosh [Sat, 13 Feb 2016 09:02:16 +0000 (11:02 +0200)]
wic-image-minimal: update .wks to boot by qemu
With below list of changes wic-image-minimal can be boot by qemu:
- Changed device name sda -> vda.
- Added root=/dev/vda2 to the kernel command line.
- Changed mount point for core partition to /mnt to have it
mounted on boot time.
Ed Bartosh [Sat, 13 Feb 2016 09:02:12 +0000 (11:02 +0200)]
qemurunner: add parameter to method 'start'
QemuRunner requires pair of ip addresses provided through kernel
commandline for method 'start' to work. These ip addresses are
used to connect to the image using ssh and run tests there.
However, this functionality should not be mandatory as testing
doesn't always require ssh connection. Some tests can be run using
serial console.
Added new parameter 'get_ip' to QemuRunner.start to make it possible
to skip getting pair of ip addresses from kernel command line. This
should allow oe-selftest to test images without modifying kernel
command line.
Ed Bartosh [Sat, 13 Feb 2016 09:02:09 +0000 (11:02 +0200)]
runqemu: don't set KERNEL for wic images
Wic images should be boot as is, without pointing qemu to the kernel
binary. Current code doesn't use kernel, but sets KERNEL variable and
shows kernel path in the console output. This can confuse users.
Changed runqemu and runqemu-internal code to avoid setting KERNEL
variable and show kernel path.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
