Unlike the big jump in version (4 -> 4-6), blktool is actually quite stable since
version 4 (2005). All the changes in 4-6 are about typo fix and debian package
control enhancement.
Fixed metadata accordingly.
Signed-off-by Kevin Tian <kevin.tian@intel.com>
- update metadata. license checksum is skipped, as pax-utils is depended by do_package task itself.
I.e. the 1st do_package will be run after pax-utils-native is built. So far checksum verification
is included in do_package task
- no need to override {S} since {S} uses {BPN}
- no need to define "_GNU_SOURCE" which has been included by source
tar ball. Also remove do_compile override accordingly
- remove recipe internal md5sum, which is not used by Poky
Signed-off-by Kevin Tian <kevin.tian@intel.com>
om-gta01, om-gta02, nokia700, nokia800 and mx31litekit no longer build and we
don't have a maintainer for them so move them to meta-extras
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Previously, the cooker object was created before the environment was
cleaned, saving everything that was in the environment and dumping
into the run scripts.
The patch ensures that the cooker gets a cleaned environment when it's
created.
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
In order to move the environment cleaning, which wants to log a
message, before cooker creation, the logging facility initialization
needs to happen earlier. So, it is now in init_logger in utils.py and
called from bitbake before the creation of the data object.
It also seems more correct to initialize a global facility like this
from a more global context than the creation of an object, of which
there could theoretically be many.
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Run udhcpc results in
udhcpc (v1.15.3) started
/etc/udhcpc.d/50default: line 37: syntax error: unexpected "done" (expecting "fi")
run-parts: /etc/udhcpc.d/50default exited with code 2
Signed-off-by: Enric Balletbo i Serra <eballetbo@gmail.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
VMware SVGA driver needs to have same depth between the host and the guest. Or put in
other word, the depth read by the guest is the value read from host. The guest is not
allowed to change virtual depth to other value. With DefaultDepth option xorg.conf,
vmware driver rejects to work with suggestion "Please do not specify a depth on the
command line or via the config file".
Signed-off-by Kevin Tian <kevin.tian@intel.com>
VMware SVGA presents to the guest with the depth of the host surface it renders
to, and rejects to work if the two sides are mismatched. One problem is that
current VMware VGA may calculate a wrong host depth, and then memcpy from virtual
framebuffer to host surface may trigger segmentation fault. For example, when
launching Qemu in a VNC connection, VMware SVGA thinks depth as '32', however the
actual depth of VNC is '16'. The fault also happens when the host depth is not
32 bit.
Qemu <4b5db3749c5fdba93e1ac0e8748c9a9a1064319f> tempts to fix a similar issue, by
changing from hard-coded 24bit depth to instead query the surface allocator
(e.g. sdl). However it doesn't really work, because the point where query
is invoked is earlier than the point where sdl is initialized. At query time,
qemu uses a default surface allocator which, again, provides another hard-coded
depth value - 32bit. So it happens to make VMware SVGA working on some hosts,
but still fails in others.
To solve this issue, this commit introduces a postcall interface to display
surface, which is walked after surface allocators are actually initialized.
At that point it's then safe to query host depth and present to the guest.
Signed-off-by Kevin Tian <kevin.tian@intel.com>
On an F13 host with glib-config installed pkgconfig-native can get into a
horrible state with recursive calls between pkg-config and glib-config.
The patch adds a configure time option to disable legacy script support in
pkgconfig and makes use of the option for Poky.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
cross-canadian packages need to look for their SOLIBS in the nativesdk
sysroot so that dependencies are correctly picked up and meta-toolchains are
correctly built.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
The dependencies list in the introduction was missing chrpath and mercurial.
Also adds a note about the packages required to build qemu-native.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
* Remove additonal binaries known to cause "strip command failed"
errors during do_package on cross platforms.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Zhai Edwin
Kevin Tian
Yu Ke
Dexuan Cui
Joshua Lock
Jeff Dike
Enric Balletbo i Serra
Richard Purdie
Scott Garman