Richard Purdie [Tue, 5 Nov 2013 22:08:04 +0000 (22:08 +0000)]
package_rpm: Remove need for locking
Currently if multiple package tasks are running against a recipe, package_rpm
is restricted to the slowest speed of them due to the locking. This patch
explicitly ignores the opkg/debian artefacts and hence allows a speedup.
It also removes an issue were a Ctrl+C interrupting a deb.ipk packaging task
would end up with CONTROL/DEBIAN files in the spec file resulting in a build
failure.
Richard Purdie [Tue, 5 Nov 2013 22:09:51 +0000 (22:09 +0000)]
toolchain-scripts/meta-environment: Merge toolchain_create_sdk_env_script and the for_installer variant
Having two scripts which do basically the same thing is a nightmare. This merges
them together. It also makes the sysroot location a variable in its own right
which may be more useful for end users wanting to change sysroot.
Paul Eggleton [Tue, 5 Nov 2013 10:15:20 +0000 (10:15 +0000)]
zisofs-tools-native: fix meta fields
* Drop redundant DESCRIPTION (same as SUMMARY)
* Set SUMMARY to slightly more descriptive value borrowed from Fedora
* Fix HOMEPAGE URL (repeated http://)
Bruce Ashfield [Tue, 5 Nov 2013 18:47:50 +0000 (13:47 -0500)]
linux-yocto/3.10: fix qemuarm boot and spurious mips build warning
This update fixes two issues:
a) qemuarm boot failure
v3.10.13 picked up a patch for arm versatile interrupt mappings that fixes
the emulator boot out of the box. But it interacts badly with our previous
fix for the issue. Reverting the existing patch and going with the mainline
solution fixes the boot.
b) qemumips build warning and failure
Depending on the build host and compiler, the build of menuconfig throws
an potentially uninitialized variable warning. That warning causes an
error on archs with -Werror. We can do a trivial change to avoid the
warning all together (initilize it to null), and keep everyone happy.
Chris Patterson [Sat, 2 Nov 2013 19:52:13 +0000 (15:52 -0400)]
qemu: upgrade to 1.6.1
This update also drops the following patches which appear to have
been resolved upstream:
- ftd_header.patch
- target-i386-Fix-aflag-logic-for-CODE64-and-the-0x67-.patch
- target-ppc_fix_bit_extraction.patch
Qemu no longer uses the i386.ld and x86_64.ld linker scripts
and the .interp section should now have a 0x1000 size with the
proper path. Therefore, for nativesdk-qemu, the following
patch should no longer be required and is also dropped:
- relocatable_sdk.patch
Lu Chong [Sat, 2 Nov 2013 08:30:28 +0000 (16:30 +0800)]
ppp: Add two structures in if_pppol2tp.h
Some further structure definitions are needed in include/linux/if_pppol2tp.h for
IPv6 support, else we would get the error as below:
In file included from plugin.c:53:0:
bitbake_build/tmp/sysroots/intel-x86-64/usr/include/linux/if_pppox.h:84:26:
error: field 'pppol2tp' has incomplete type
struct pppol2tpin6_addr pppol2tp;
^
bitbake_build/tmp/sysroots/intel-x86-64/usr/include/linux/if_pppox.h:99:28:
error: field 'pppol2tp' has incomplete type
struct pppol2tpv3in6_addr pppol2tp;
^
make[2]: *** [plugin.o] Error 1
Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Stefan Stanacar [Fri, 1 Nov 2013 10:37:56 +0000 (12:37 +0200)]
lib/oeqa: add oeTest superclass
Add oeTest superclass, make oeRuntimeTest inherit that and
make the necesarry adjustments. Tests in lib/oeqa/runtime don't
change, they still inherit oeRuntimeTest.
We should do this because oetest.py in the future can be a base module
for more stuff than oeRuntimeTest.
Xufeng Zhang [Fri, 1 Nov 2013 04:25:17 +0000 (12:25 +0800)]
kernel.bbclass: Delay rm_work to run after do_bundle_initramfs
Since kernel will build twice when we are trying to bundle kernel
and initramfs together after commit 609d5a9ab("kernel.bbclass,
image.bbclass: Implement kernel INITRAMFS dependency and bundling"),
thus, the second building for kernel would fail if rm_work is done
previously.
To fix this problem, we need to make do_bundle_initramfs task run
before do_rm_work task.
package.bbclass: Fix split_and_strip_files when file has single quote (')
Fix false error report when a file that has a single quote by escaping
the single quote. Some packages might install files with quotes, such
as music files and other types, that will cause the problem.
Signed-off-by: Felipe F. Tonello <eu@felipetonello.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: toaster: enable required classes in the toaster startup script
In order to use toaster, now you have to set INHERIT+="toaster buildhistory"
To keep it simple, I've done some changes in order to automate it. When toaster
is started, this line is added to a new file called toaster.conf.
This file is passed to the bitbake server with the --postread parameter.
Based on a patch by Cristiana Voicu <cristiana.voicu@intel.com>
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: cooker: do not recreate recipecache in buildfile mode
When building a single file, the cooker will recreate
the recipecache from scratch.
I suspect this is a remnant of past code, since:
* the current recipecache works fine
* the new recipecache will not have all the fields as
requested by HOB_EXTRA_CACHES setting
This patch disables recreating the recipecache, leading
to shorter times when building single build files
(-b option) and better compatibility with Toaster.
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: cooker: add data to the dependency tree dump
Toaster needes to record extra data that needs to
be moved at the time of the dependency tree dump.
This data includes:
* layer priorities for recording in the layer section
* the inherit list for each PN which allows to determine
the type of the PN (regular package, image, etc).
This patch adds this data to the dependency tree dump.
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: toaster: fixes for null values from events
Some of the data values may come of as None through the event system,
and the UI would encounter a problem saving the Configuration.
It would be trying to save these values as NULL in the
database, which is not allowed.
This patch adds more verification for data coming through
the event system.
Other minor updates:
* update for the event model from toaster.bbclass
* minor code flow fix in the event system
Adding a new bbclass that will collect and send relevant
data from the task context to the Toaster UI.
This bbclass consists of postfuncs that get executed
right after the main task func, and in the same context.
This allows data gathering in a synchronous manner during
the build, guaranteeing data integrity. This approach also
preserves the task signatures.
The data is moved to the UI through the event system.
There is no performance impact if the class is disabled.
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Tue, 29 Oct 2013 15:26:54 +0000 (15:26 +0000)]
image_types: Improve dependency handling between types (and use for sum.jffs2)
We're seeing a pattern of one image type needing to depend on another
type. A good example is jffs2 and sum.jffs2. This patch makes sum.jffs2
depend on jffs2 which will then allow a EXTRA_IMGAGECMD to be set for
sum.jffs2 individually without changing the jffs2 command. This allows the
-pad option to be configured differently.
Cristiana Voicu [Fri, 1 Nov 2013 09:18:45 +0000 (11:18 +0200)]
bitbake: hob: populate error_msg when hob receives a CommandFailed event
When Hob receives a bb.command.CommandFailed event, it doesn't show any error,
because the error_msg is empty. If so, it is hard to detect the issue, because
Hob continues to run till it blocks because of an information gap.
bitbake: fetch2/svn.py: use log instead of info to retrieve revision
We have faced a corner case situation where the 'last changed
revision' returned from svn info is wrong. It happens when the last
revision is a directory move. e.g. if we assume that the svn
repository at revA has root/x/y/z/foo/bar and it is moved to
root/a/b/c/foo/bar in revB, then svn info 'last change revision' will
return revA. As such when using AUTOREV, we are going to attempt to
retrieve root/a/b/c/foo/bar (as per SRC_URI) but at revA when it did
not exist.
So this patch changes how we retrieve the latest revision and uses
'svn log --limit 1' which gives correct result in all tested cases.
Maxin B. John [Thu, 31 Oct 2013 15:01:25 +0000 (08:01 -0700)]
adt-manual: Added note for static builds using -c populate_sdk
Documentation fix for [YOCTO #5347]
SDK created useing the "-c populate_sdk" will not support static
binary build without proper staticdev library packages.
I have added a note to inform the user about this limitation.
Scott Rifenbark [Wed, 30 Oct 2013 18:42:59 +0000 (11:42 -0700)]
dev-manual: Updates to Toaster section
Partial fix for [YOCTO #4414]
I put in the API stuff as well as made sure the other comments
for the dora-toaster branch and temporariness of the GUI were
mentioned. Probably more tweaks before this section settles
out.
Scott Rifenbark [Wed, 30 Oct 2013 17:35:01 +0000 (10:35 -0700)]
dev-manual: Edits to the toaster section
Partial fix for [YOCTO #4414]
Got some feedback on the section and added a step that the user
needs to checkout the dora-toaster branch after clonine poky.
Also, that the Django version is specific and not the listed
version +. Finally, a bit of wording to note that the GUI is
temporary for this release.
Scott Rifenbark [Wed, 30 Oct 2013 15:09:53 +0000 (08:09 -0700)]
ref-manual: updated the list of where to get YP release
Partial fix for [YOCTO #5368]
The list that summarized where to get YP release did not include
the source repositories. It basically just listed tarball
areas. Now that cloning the Git repo of poky is the preferred
method for obtaining YP, I made sure that this area was the
first spot listed and called out as the preferred method.
Scott Rifenbark [Tue, 29 Oct 2013 18:27:38 +0000 (11:27 -0700)]
dev-manual, mega-manual: Updated kernel flow (text and figs)
Partial fix for [YOCTO #5368]
Updated the figure to not have the tarball method in there
for setting up poky repo locally. Also, added specific references
to the environment setup scripts.
Scott Rifenbark [Tue, 29 Oct 2013 17:51:01 +0000 (10:51 -0700)]
dev-manual, mega-manual: Updated BSP Development figure
Partial fix to [YOCTO #5368]
I updated the workflow so that it does not have the tarball
extraction option to set up local copies of poky and meta-intel.
The figure is housed in dev-manual and mega-manual.
Scott Rifenbark [Tue, 29 Oct 2013 16:45:24 +0000 (09:45 -0700)]
dev-manual: Edits to the "Source Directory" term
Fixes [YOCTO #5368]
Partial fix to the tarball removal issue. I rewrote parts of
this term's definition to slightly de-emphasize tarball expansion
as a method to set up the Source Directory on the local machine.
Scott Rifenbark [Tue, 29 Oct 2013 15:53:14 +0000 (08:53 -0700)]
dev-manual: Edits to "Yocto Project Source Repositories" section
Fixes [YOCTO #5368]
This is a partial fix to the removing tarball setup method issue.
I have modified the "Yocto Project source Repositories" section to
de-emphasize the tarball installation method for poky and meta-intel.
We cannot remove these obviously because the download page of the
website gives the use access to tarballs. Also, the Index of
Releases basically does the same thing. So, we can't ignore the
fact that they are there. So, I added a note basically saying we
recommend the Git method for creation of poky and meta-intel on the
development system.
Scott Rifenbark [Tue, 29 Oct 2013 15:14:12 +0000 (08:14 -0700)]
dev-manual: Removed tarball method for installing meta-intel
Fixes [YOCTO #5368]
Partial fix for this issue, which is removal of the tarball install
methods for poky and now evidently meta-intel. This commit removed
the tarball install step for meta-intel in the "Supported Board
Support Packages (BSPs):" bullet item in the getting setup section.
Scott Rifenbark [Tue, 29 Oct 2013 14:37:31 +0000 (07:37 -0700)]
dev-manual: Removed tarball method for poky in setup section
Fixes [YOCTO #5368]
Partial fix for the bug. This part removed the tarball install
method from the getting setup section of the second chapter. I
did some rewriting to smooth it out.
Scott Rifenbark [Fri, 25 Oct 2013 16:43:43 +0000 (09:43 -0700)]
adt-manual: Edits to "Extracting the Root Filesystem" section
This section was a bit confusing. I added some lists to make
it clearer when this step is necessary. I also added some more
detail on where to find the setup script.
Scott Rifenbark [Thu, 24 Oct 2013 20:15:24 +0000 (13:15 -0700)]
adt-manual: Edits to the "Using a Cross-Toolchain Tarball" section.
This section was not quite right for the installation method
after obtaining the tarball. There was some old stuff in there
and it didn't mention the fact that the script asks you what
directory you want to install into.
Scott Rifenbark [Thu, 24 Oct 2013 17:44:52 +0000 (10:44 -0700)]
adt-manual: Fixed toolchain path in example
The path used for the toolchain was wrong. The string
"toolchain" appears in the path. I was not informed of this
before locking down 1.5 release doc changes. I have updated
the path in the "Using a Cross-Toolchain Tarball" section.
Occured twice.
Scott Rifenbark [Thu, 24 Oct 2013 16:51:38 +0000 (09:51 -0700)]
adt-manual: Removed tarball method from "Getting the ADT Installer Tarball"
Fixes [YOCTO #5368]
Partial fix to this issue.
This section demonstrated how to build the ADT Installer tarball
using BitBake by downloading the poky release tarball. I updated
the section to use the method where you use Git to clone the
poky repo and then check out the current release as a branch.
Scott Rifenbark [Thu, 24 Oct 2013 16:09:42 +0000 (09:09 -0700)]
adt-manual: Fixed wording for getting the ADT tarball
Poorly worded opening sentence for the "Getting the ADT Installer
Tarball" section. I re-wrote this to remove the confusing link
to the Index of Releases.
Scott Rifenbark [Thu, 24 Oct 2013 15:42:21 +0000 (08:42 -0700)]
yocto-project-qs: Updated the "Super User" section for no tarballs
Fixes [YOCTO #5368]
Partial fix for this issue. This section had two options for
setting up the Source Directory (tarball and cloned repo). I
removed the tarball option.
Also, I did some routine formatting as well as verified that
the example runs on a more recent Linux distro. Previously, the
example was confirmed and stated that it ran on 10.04 Ubuntu.
Well, this distro is not even in the supported list any longer
so I ran it on a 12.04 Ubuntu machine and stated that.
Discovered that the string "toolchain" is in the pathname of the
toolchain installers from the downloads area. This invalidated
the explanation of how the installer files are named and the
actual examples themselves. I fixed it all.
Scott Rifenbark [Wed, 23 Oct 2013 22:44:48 +0000 (15:44 -0700)]
yocto-project-qs: Updated "Building an Image" example to use Git repo
Fixes [YOCTO #5368]
Partially addresses this issue, which is removal of examples that
use a poky tarball. I changed the example so that it clones the
upstream poky repo and then checks out a local branch named for
the most recent release.
Scott Rifenbark [Wed, 23 Oct 2013 17:41:09 +0000 (10:41 -0700)]
documentation: Changed Note for most recent manual
Fixes [YOCTO #5368]
Changes partially address this issue, which is the removal of
tarball installations for poky. The notes at the beginning of
the YP manuals suggested that the tarball version of a manual
might lag the version found on the website. Because we are
discouraging installing poky/documentation from a tarball now,
I have re-written the note to be generic and suggest simply that
for the most recent version of the manual associated with the
release, see the manual on the website.
Scott Rifenbark [Tue, 22 Oct 2013 15:58:21 +0000 (08:58 -0700)]
dev-manual: Added -ptest to list of complementarty packages
Added the '-ptest' complementary package to the list of packages,
which included '-dev' and '-dbg' when using inherit packagegroup.
Robert P. J. Day pointed out the code in the OE packagegroup.bbclass
class that showed these three packages all together.
Scott Rifenbark [Tue, 22 Oct 2013 15:49:31 +0000 (08:49 -0700)]
dev-manual: Uncommented the Toaster GUI section.
Removed the comments for the section that describes how the
Toaster works with a GUI. I also commented out the smaller
section that was used in place of the GUI section before it
was fully functional.
Scott Rifenbark [Mon, 14 Oct 2013 18:18:04 +0000 (11:18 -0700)]
profile-manual: Added note about SystemTap ssh connectivity
Fixes [YOCTO #4409]
Added a note into the Setup section for SystemTap that tells
how ssh connection is assumed. Also provided a link to the
wiki page that basically replicates all the same information that
is in the section.
Scott Rifenbark [Mon, 14 Oct 2013 16:55:44 +0000 (09:55 -0700)]
dev-manual: Added note for BB Commander project location.
Fixes [YOCTO #5203]
Adding a BB Commander project location that is the same as your
Eclipse workspace causes an error. I have added a note warning
the user to not do this.
The actual file listings for the formfactor_0.0.bb and
formfactor_0.0.bbappend files had changed. I updated the listings
to match the actual files with the release.
Jason Wessel [Wed, 30 Oct 2013 17:35:17 +0000 (12:35 -0500)]
grub-efi.bbclass: Fix startup.nsh to work on more EFI revs
Some revs of the EFI firmware + shell do not automatically setup the
path in a such a way as to execute a binary without an absolute
reference like "FS0:\EFI\BOOT\bootx64.efi". All the versions that I
have tested work properly by simply calling the binary which is in the
EFI\BOOT directory by name like "bootx64.efi".
The error you see on the console looks like the following:
startup.nsh> EFI\BOOT\bootx64.efi
'EFI\BOOT\bootx64.efi' is not recognized as an internal or external command, operable program, or batch file
Shell>
This patch simply drops the EFI\BOOT for greater compatibility.
Jacob Kroon [Wed, 30 Oct 2013 00:57:11 +0000 (01:57 +0100)]
update-rc.d.bbclass: Cleanup package scripts
* Add proper preinst script
* Use -n "$D"/-z "$D" checks throughout the scripts
* Only set OPT in cases where its used
* Don't pass unnecessary -f to update-rc.d in postrm script
* Remove outdated comment
grub-efi.bbclass: Fixes GRUB_IMAGE when using boot-directdisk class
When boot-directdisk class is used and EFI boot is set the
grub-efi-${TRANSLATED_TARGET_ARCH}-native need to be dependent.
Allowing GRUB_IMAGE to be created and bootia32.efi got from the
image directory.