Paul Eggleton [Fri, 22 Mar 2013 19:53:52 +0000 (19:53 +0000)]
classes/buildhistory: implement history collection for SDKs
SDKs are constructed in a similar manner to images, and the contents can
be influenced by a number of different factors, thus tracking the
contents of produced SDKs when buildhistory is enabled can help detect
the same kinds of issues as with images.
This required adding POPULATE_SDK_POST_HOST_COMMAND and
SDK_POSTPROCESS_COMMAND variables so that data collection functions can
be injected at the appropriate points in the SDK construction process,
as well as moving the list_installed_packages and
rootfs_list_installed_depends functions from the rootfs_{rpm,ipk,deb} to
the package_{rpm,ipk,deb} classes so they can also be called during
do_populate_sdk as well as do_rootfs.
Scott Rifenbark [Fri, 22 Mar 2013 14:09:31 +0000 (07:09 -0700)]
dev-manual: Updated the "Core System Development" section
Added a new bullet as a tip for best practices that addresses
how we address bug 3071 and 3274. We are suggesting they enable
a PR Service if they are using continually incrementing PR values
when package feeds are published or used.
Scott Rifenbark [Thu, 21 Mar 2013 13:47:31 +0000 (06:47 -0700)]
dev-manual: Reword for when to use BBMASK.
Changed the wording on when a user would consider using
the BBMASK variable. It is more suited for excluding things
that cause problems rather than for speeding up build time.
Scott Rifenbark [Wed, 20 Mar 2013 19:17:39 +0000 (12:17 -0700)]
profile-manual: Updates to LTTng section setup
With dylan, the two patches are no longer required. However,
the information to view traces still holds true regarding
using Eclipse's Juno. Updated appropriately.
Scott Rifenbark [Mon, 11 Mar 2013 19:27:07 +0000 (12:27 -0700)]
adt-manual: Added note to indicate ADT is distribution neutral.
Cleared up some old wording that was confusing the build
system with "Poky". Also, added a note at the front of the
manual to be clear that the ADT is distribution-neutral.
Scott Rifenbark [Wed, 6 Mar 2013 18:28:37 +0000 (10:28 -0800)]
dev-manual: Created list for other layer mods for other distros
The final paragraph of the "Creating Your Own Distribution" really
should have been in list form and should have some cross-refs
for other parts of the manual. The paragraph is now in list
form and there are some references.
Scott Rifenbark [Wed, 6 Mar 2013 18:26:55 +0000 (10:26 -0800)]
dev-manual: Added notes about creating your own distro
Added a couple of notes to point out the ease of creating your
own distro and not just relying on a Poky distribution. One
note is at the very beginning of the manual and mentions
Angstrom as an example of a distro based on the YP. The
other note is at the beginning of the second chapter.
Mark Hatle [Tue, 19 Mar 2013 20:17:48 +0000 (15:17 -0500)]
vte: Fix conflict between FILES_${PN}-dbg and FILES_vte-dbg
Due to quarks with the way bitbake handles variable key values, the
hard coded FILES_vte-dbg or automatic FILES_${PN}-dbg could replace
each other, leaving the system in an inconsistent state.
Robert Yang [Wed, 20 Mar 2013 06:31:05 +0000 (14:31 +0800)]
local.conf.sample.extended: update for disk monitor
The previous disk monitor is based on the disk, and one disk only can
have one action, now it is based on the path, so we remove the additional
comments from local.conf.sample.extended
Zhenhua Luo [Wed, 20 Mar 2013 07:52:12 +0000 (15:52 +0800)]
fix march sanity check issue
1. check if gcc_test is really generate before os.remove("gcc_test") to avoid
following error:
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
Traceback (most recent call last):
File "check_sanity_eventhandler(e)", line 4, in check_sanity_eventhandler(e=<bb.event.ConfigParsed object at 0x3151450>)
File "sanity.bbclass", line 107, in check_sanity(sanity_data=<bb.data_smart.DataSmart object at 0x11ba110>)
File "sanity.bbclass", line 22, in check_gcc_march(sanity_data=<bb.data_smart.DataSmart object at 0x11ba110>)
OSError: [Errno 2] No such file or directory: 'gcc_test'
2. set result to False when build failed with -march=native to ensure
-march=native is appended to BUILD_CFLAGS when host gcc really supports this flag,
otherwise following error appears when build native packages.
| cap_text.c:1: error: bad value (native) for -march= switch
| cap_text.c:1: error: bad value (native) for -mtune= switch
Michel Thebeau [Wed, 20 Mar 2013 15:32:02 +0000 (11:32 -0400)]
routerstationpro: use KERNEL_IMAGE_MAXSIZE to test the image
routerstationpro is limited to 16mb flash size. Exceeding that size may
not be noticed immediately, which we don't want.
"The current latest kernel for the routerstationpro machine is far
beyond the 16MB of it's flash size [0]. I think it would be good to
[test if the size of the image is above that size]."
Setting this variable will enable the do_sizecheck task and produce an
error when the image is too large:
"ERROR: This kernel (size=90230265 > 16777216) is too big for your
device. Please reduce the size of the kernel by making more of it
modular."
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Darren Hart [Tue, 19 Mar 2013 22:15:06 +0000 (15:15 -0700)]
mkefidisk: Use msdos partition tables
While GPT works fine when writing to actual media, it cannot be reliably
used for distributing disk images as it requires the backup table to be
on the last block on the device, which of course varies from device to
device. Use MSDOS tables instead.
Use mkfs to label the filesystems as msdos tables do not support
partition labeling.
Darren Hart [Tue, 19 Mar 2013 22:15:05 +0000 (15:15 -0700)]
mkefidisk: Remove startup.nsh
Most firmware implementations use the EFI specified
EFI/BOOT/bootia32.efi (and similar) boot paths. Only broken firmware
uses different paths for removable media. In those cases, the user can
add their own startup.nsh.
For the compliant case, selecting "Shell" from the EFI boot menu should
go to the shell.
Darren Hart [Tue, 19 Mar 2013 22:15:04 +0000 (15:15 -0700)]
mkefidisk: Always use rootwait and document kernel parameters used
Without a reliable way of knowing if the target device with be an
asyncronous block device on the target (MMC or USB), err on the side of
caution of always specifcy "rootwait", ensuring the kernel will wait for
the device to appear and not abort if it hasn't appeared in time for
mount.
Document the remaining kernel parameters added by this script on the
same line as rootwait.
Darren Hart [Tue, 19 Mar 2013 22:15:03 +0000 (15:15 -0700)]
mkefidisk: Boot with ro kernel parameter instead of rw
There is no need to boot with "rw". Booting with "ro" will allow for
fsck to be run during boot, and a proper /etc/fstab will still ensure
the rootfs is "rw" by the time the user can interact with the system.
Change the "rw" to "ro" in the kernel parameters specified in the
generated grub.cfg file.
Fixes [YOCTO 4036] mkefidisk.sh hardcodes 'rw' as root mount option
Darren Hart [Tue, 19 Mar 2013 22:15:02 +0000 (15:15 -0700)]
mkefidisk: Always specify a root= kernel parameter
The current script only replaces an existing root= kernel parameter
which can result images created without a root= paremeter, even though
the script expects a target rootfs parameter.
Rather than replacing the root= parameter, delete the root= parameter if
it exists, then append an appropriate root= parameter.
Fixes [YOCTO 4035] mkefidisk.sh forgets to add root= parameter
Ross Burton [Thu, 21 Mar 2013 09:24:25 +0000 (09:24 +0000)]
consolekit: don't inherit gnome
By inheriting gnome this package was build-depending on
gtk-update-icon-cache-native, gconf, gconf-native, shared-mime-info and
hicolor-icon-theme for no reason. Change this to inherit autotools pkgconfig to
reduce the build-dependencies.
Also, add a missing dbus-glib build-dependency that was previously pulled in
through something in the gnome class.
package_{ipk, deb, rpm}: drop the TARGET_OS conditional
The tclibc file for uclibc already empties IMAGE_LINGUAS, so there's no point
to this conditional as far as I can tell, and it can cause issues for certain
values of TARGET_OS.
This was removed from package_rpm and package_ipk years ago, and shouldn't be
needed, installing the packages from package_linguas should be sufficient.
Coreutils does not depend on ACL but also does not disable it. Effect is
that from time to time I have a copy in sstate-cache which got built
with ACL and then I have problem while building images or sdk:
| Collected errors:
| * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-core-standalone-hhvm-sdk-target:
| * libacl1 (>= 2.2.51) *
| * opkg_install_cmd: Cannot install package packagegroup-core-standalone-hhvm-sdk-target.
Paul Eggleton [Thu, 21 Mar 2013 15:43:40 +0000 (15:43 +0000)]
perl: avoid splitting out .debug directories as packages
The recursive parameter is set to True, the regex for the first call to
do_split_packages matches any path under ${libdir}/perl/${PV}/auto/, and
the .debug directories contain .so files, so each one was getting picked
up as a package. Change the regex to disallow dots in the path beneath
auto/ and thus avoid the .debug directories.
Jukka Rissanen [Fri, 22 Mar 2013 08:11:41 +0000 (10:11 +0200)]
connman-conf: Move the setup script into /usr/lib/connman
The /etc/connman is not suitable for the setup script.
There are other connman related scripts in /usr/lib/connman
so moving the wired setup script there.
Richard Purdie [Tue, 5 Mar 2013 16:48:11 +0000 (16:48 +0000)]
distro: Add separatebuilddir.inc
Going forward its going to be useful to separate build data from source data
in those autotooled projects which support it. Unfortunately there is a lot
of breakage so for now, this starts the creation of an opt in list which
we can iterate over enable more recipes over time.
Richard Purdie [Thu, 21 Mar 2013 14:29:57 +0000 (14:29 +0000)]
scripts/qemu-testlib: Add more debugging information
This extra information should allow better forensics if the sanity tests
fail as they're currently doing occasionaly on the autobuilder for unknown
reasons.
The patch also tightens up certain checks to remove pointless noise and
error output from the logs.
Richard Purdie [Wed, 20 Mar 2013 22:58:30 +0000 (22:58 +0000)]
scripts/runqemu-internal: Fix lock races
There are two problems here. Firstly the grep command is unanchored so
pid 345 will match against 12345 and so on.
The second issue is that there are several context switched between attempting
the lock and then writing the pid to it.
Between the two issues, there were issues appearing on the autobuilder due
to these conflicts. This patch replaces the mechanism with flock on fd 8
which should be a safer mechanism to use.
Alexandru DAMIAN [Tue, 12 Mar 2013 09:56:02 +0000 (09:56 +0000)]
grep: Always use locale.h
The changes in the grep 2.5 configuration always leave out
HAVE_LOCALE_H - it has been removed from other files, but
not from everywhere.
This leads to a crash in certain configurations where the
size of int is not the size of pointer; this happens because
setlocale() is used while being undeclared.
Richard Purdie [Wed, 20 Mar 2013 11:48:53 +0000 (11:48 +0000)]
runqemu: Improve error handling/exit codes
runqemu-internal is sourced so should be returning with an error code in
case of errors. runqemu needs to deal with this.
This patch fixes up the various error paths so we're consistent and get
a sane exit status for runqemu which helps a lot in its use in the qemu
runtime testing on the autobuilder.
Richard Purdie [Wed, 20 Mar 2013 10:58:24 +0000 (10:58 +0000)]
qemuimage-testlib: Add extra debugging and sanity check
Check for a zero IP address since its clearly incorrect if that value
is found. Also add debugging for cases where we can't find the qemu
process. A process listing is handy to help understand what the problem
might be.
Richard Purdie [Wed, 20 Mar 2013 09:27:39 +0000 (09:27 +0000)]
qemuimage-testlib: Add delay to work around races in qemu startup
Qemu changes pid when starting up. On a loaded machine, this can result
in the incorrect pid being returned. Since qemu will take a few seconds to
boot anyway, we might as well delay a short while and allow things to settle
which should fix various race issues being seen on the autobuilder.
Martin Jansa [Wed, 13 Mar 2013 20:01:51 +0000 (21:01 +0100)]
bitbake: runqueue: Use taskData.fn_index[depdata] instead of uninitialized dep
* dep variable was removed in
commit 3190cb83e2af195a464f669c5aa8aedbf795160e
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Wed Jun 27 11:04:06 2012 +0100
taskdata: Add gettask_id_fromfnid helper function
This is like gettask_id but doesn't require translation of fnid -> fn
first which the function then translates back. This gives a sizeable
performance improvement since a significant number of lookups are avoided.
* now it fails completely instead of showing which task is missing
Cristiana Voicu [Mon, 11 Mar 2013 13:06:58 +0000 (15:06 +0200)]
bitbake: hob: some settings in Hob are not remembered
Some settings in Hob were not saved in Bitbake and they were not displayed
correcty in Hob, because Hob used some other variables with the extension "_HOB".
I have removed this, in order to have a consistency for the variables.
ALso, I called a function to load the extra variables saved in .hob/template_default.hob.
Richard Purdie [Tue, 19 Mar 2013 20:54:33 +0000 (20:54 +0000)]
scripts/qemutestlib: Add better process debugging and fix process group issue
In single testing with a shutdown scenario the processes are cleaned up correctly
but the manual cleanup fall back used for a minimal image do not work properly.
This patch fixes the kill commands to revert to non-process groups, fixing
the hung process issues that were occuring.
Robert Yang [Sat, 16 Mar 2013 08:07:41 +0000 (16:07 +0800)]
bitbake: utils.py: fix BB_ENV_WHITELIST
The BB_ENV_WHITELIST doesn't work well and flushes BB_ENV_EXTRAWHITE,
here is an example:
$ export BB_ENV_WHITELIST
$ export BB_NUMBER_THREADS=10 (or other value)
Edit conf/local.conf, change "BB_NUMBER_THREADS =" to "BB_NUMBER_THREADS ?="
$ bitbake -e | grep '^BB_NUMBER_THREADS ='
we will notice that BB_NUMBER_THREADS' value doesn't change, though
BB_NUMBER_THREADS in both BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE.
This is because the "approved" inside the function approved_variables
doesn't include BB_ENV_WHITELIST or BB_ENV_EXTRAWHITE when
BB_ENV_WHITELIST is set (they are incuded by preserved_envvars()), so
the BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE will be removed from the env
in the first call from bin/bitbake, and when it is called again by
cooker.py, their value will be None, then the vars inside them will be
removed from the env.
Add BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE to the "approved" would fix
the problem.
Robert Yang [Fri, 15 Mar 2013 07:42:48 +0000 (15:42 +0800)]
bitbake: monitordisk.py: monitor disks based on path
The previous monitor is based on the disk, and one disk only can have
one action, this limits its function, for example we set this in the
current local.conf:
Before:
* If TMPDIR, DL_DIR and SSTATE_DIR are on the same disk partition,
only the last line "ABORT,${SSTATE_DIR},100GM,1K" works
* If TMPDIR, DL_DIR and SSTATE_DIR are on the different disk partitions,
only the last three lines (ABORT) work.
These are not what we expect, now:
* We monitor the disk based on the path and action, so all the six lines
will work no matter whether they are on the same disk partition or
not.
* The out put format will be:
WARNING: The free space of /path/to/directory (device) is running low (XXGB left)
Maxin B. John [Tue, 19 Mar 2013 12:37:04 +0000 (13:37 +0100)]
harfbuzz: update the license information
harfbuzz is using the 'Modern Variants' of MIT License:
https://fedoraproject.org/wiki/Licensing:MIT?rd=Licensing/MIT#Modern_Variants
We can update the LICENSE as 'MIT & ICU'.
Fixes this warning:
WARNING: harfbuzz: No generic license file exists for: Old-MIT in any provider
WARNING: harfbuzz: No generic license file exists for: UCDN in any provider
WARNING: harfbuzz: No generic license file exists for: HarfBuzz-old in any provider
Richard Purdie [Tue, 19 Mar 2013 13:22:59 +0000 (13:22 +0000)]
perf: Fix parsing error
Due to the use of ${@...} the code will try and expand this when
performing the initial parsing. If the sysroot doesn't exist with
an existing kernel, this will fail at parsing time.
Sinec we're already in python, just remove the ${@....} wrapping
and then we execute at do_package time which is what we want.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
