Paul Eggleton [Thu, 11 Oct 2012 13:27:27 +0000 (14:27 +0100)]
local.conf.sample: add PATH to SSTATE_MIRRORS comments
The shared state cache as pointed to by SSTATE_DIR by default now has
two-character subdirectories to prevent there being an issue with too
many files in the same directory; also, native sstate packages will go
into a subdirectory named using the distro ID string. If you copy the
newly structured sstate cache to a mirror location (either local or
remote) and then point to it in SSTATE_MIRRORS, you need to append
"PATH" to the end of the mirror URL so that the path used by bitbake
before the mirror substitution is appended to the path used to access
the mirror.
Richard Purdie [Wed, 10 Oct 2012 21:39:36 +0000 (21:39 +0000)]
gdbm: Resolve host contamination issue
The autoconf macros detect the presence of -ldbm or -lndbm on the host
system and add the library to link against, for now good reason I can
explain.
This patch makes the build behave determinstically whether they're
present or not. Other than the extra linkage, there doesn't appear to be
any other change in behaviour from these options and they look like
dead code.
The extra linkage can cause problems where sstate is used on a machine
where the extra librbary isn't present causing build failures.
Richard Purdie [Wed, 10 Oct 2012 16:56:41 +0000 (17:56 +0100)]
pkgconfig: Drop the RREPLACES for pkgconfig-dev
This line causes pkgconfig-dev to replace pkgconfig so the package with all the files
in is replaced by one with no files. This makes no sense and hence we should just
remove this broken line.
At this point in the release, this is the safest way to fix this even if an empty -dev
package is left available.
Saul Wold [Wed, 10 Oct 2012 15:55:45 +0000 (08:55 -0700)]
eglibc: force make to use /bin/bash
The eglibc core build still has a number of issues with /bin/dash.
Recently found is both sysdeps/unix/make-syscalls.sh and it's output,
which make calls via SHELL do not play well with /bin/dash. By force
make to use /bin/bash via SHELL setting it works correctly.
Currenly known issues are: make-syscalls.sh line with a bad substitution,
which can be corrected by:
vdso_symver="$(printf '%s\n' ${vdso_symver} | sed 's/\./_/')"
Following that there is an issue with emiting a '\n' through a second
echo and then to the compiler. There maybe more issues beyond that.
Scott Rifenbark [Tue, 9 Oct 2012 18:38:35 +0000 (11:38 -0700)]
documentation: dev-manual - edits to patching kernel section plus others
Removed the temporary text in the new "Patching the Kernel" section
that was copied from the old appendix A. Fixed the PRINC variable
in the creating a new layer example.
Removed the "kernel-example-repos-generic.png" file as it describes
the bare clone method for kernel modification. We are removing
that from this manual.
The kernel workflow section was re-written to reflect that the
kernel appendix has been removed. Also, changes to the flow in
general no longer make reference to the bare clone and the copy
of the bare clone as a method used to modify the kernel.
Many links were modified in other manuals as well.
Scott Rifenbark [Tue, 9 Oct 2012 13:30:04 +0000 (06:30 -0700)]
documentation: dev-manual - Removed figures no longer needed.
The figure that shows the bare clone and the copy of the bare
clone are no longer needed. The description for the kernel
workflow has been reduced to discussing only modification of
the temporary source files. We are no longer talking about
creating a bare clone and copying it as a way to modify the
kernel in this manual. That topic will be described elsewhere.
Scott Rifenbark [Mon, 8 Oct 2012 17:14:58 +0000 (10:14 -0700)]
documentation: dev-manual, bsp-guide - Removing/Moving Appendix A
The kernel example appendix is being removed. This broke a lot
of links. For now I have moved the information into a new section
called "Patching the Kernel". I have preserved the information
by adding the old appendix file as kerne-appendix-orig.xml.
Scott Rifenbark [Mon, 8 Oct 2012 15:49:23 +0000 (08:49 -0700)]
documentation: dev-manual - Updates to configuring Kernel section
Eliminated the section A.2, which had an example of how to use
menuconfig in the kerenl example appendix. The information is
now merged into the similar section in Chapter 4 "Common
Tasks." It was decided that the Appendix A examples in the
manual were too detailed for a general development guide.
Tom Zanussi [Wed, 10 Oct 2012 00:48:24 +0000 (19:48 -0500)]
perl: add archlib_exp variable used to generate ARCHLIB_EXP in config.h
perl.c uses an ARCHLIB_EXP define to generate compile-time code that
adds the archlibexp path to @INC during run-time initialization of a
new perl interpreter.
Because we've changed this value in a temporary way to make it
possible to use ExtUtils::Embed in the target build (the temporary
value in config.sh gets re-stripped out during packaging), the
ARCHLIB_EXP value that gets generated still uses the temporary version
instead of the original expected version (i.e. becauses it's in the
generated config.h, it doesn't get stripped out during packaging like
the others in config.sh).
This creates an unmodified version called archlib_exp that gets used
by a modified config_h.SH to get the correct value into config.h
This patch uses an unmodified version of archlibexp called
archlib_exp, introduced to config.sh, which is used to generate the
correct value of ARCHLIB_EXP into config.h
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Darren Hart [Fri, 5 Oct 2012 22:30:48 +0000 (22:30 +0000)]
linux-yocto-tiny: Add tiny recipe for the 3.4 linux-yocto kernel
This recipe builds the "tiny" kernel type defined by the linux-yocto
meta-data. Support is defined for the qemux86 machine via
common-pc-tiny.scc in the linux-yocto meta branch. The resulting
kernel is 1.8 MB and boots to a serial console with with qemux86 and
core-image-minimal using the following command:
Saul Wold [Mon, 8 Oct 2012 01:07:11 +0000 (18:07 -0700)]
nfs-export-root: add explict no_subtree-check to suppress warning
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Mon, 8 Oct 2012 04:05:18 +0000 (00:05 -0400)]
linux-yocto/3.4: fix kconfig warnings and unnecessary options
Updating the kernel configuration fragments to fix the following
issues:
- remove options that are no longer in the 3.4 kernel
- disable unused, but large kernel modules
- fix kconfig audit warnings for x86 BSPs
- make uprobes reusable by multiple fragments
The following meta branch commits are represented by this update:
3da1172 uprobes: split into enable and patch fragments 17ec51a meta: cleanup invalid/obselete 3.4 CONFIG options b5cee42 meta: disable OCFS2 by default efe937e meta: drm: tag DRM options as 'hardware' 10b5155 meta: emenlow: clean emenlow configuration warnings a907b82 meta: add CONFIG_SHMEM to standard kernel config
Scott Rifenbark [Fri, 5 Oct 2012 16:35:03 +0000 (09:35 -0700)]
documentation: dev-manual - added OE_INIT_FILE and went to 3.4
In the Kernel example appendix I changed some remaining 3.2
kernel strings to 3.4. Also I added the OE_INIT_FILE variable
from poky.ent for use instead of the "oe-init-build-env" string.
Scott Rifenbark [Thu, 4 Oct 2012 20:12:57 +0000 (13:12 -0700)]
documentation: dev-manual - Created generic figures
Each time the kernel revision is bumped (e.g. 3.2 to 3.4)
Some of the figures would be out of date. The reason is they
had pathnames that included the release of the kernel.
For previous YP releases I was adding logic to the Makefile
to be sure to catch the right files dependent on the branch
from which the documents were being built. This scheme is
not scalable so I decided to make the figures generic by
adding a note within the figures explaining the place-holder
"<x.x>" as part of a pathname. Thus, three new figures were
added to the folders directories of the dev-manual and the
mega-manual. Correspondingly, the 'denzil' version of the
figures were deleted.
I modified the Makefile so that if the BRANCH is not edison
or denzil then the generic figure set is used. I have to retain
the logic for both edison and denzil to cover the case where
a user clones or sets up an edison or denzil repo and then
builds out the manuals. Basically, it had to be backwards
compatible for releases prior to danny.
Scott Rifenbark [Thu, 4 Oct 2012 17:13:42 +0000 (10:13 -0700)]
documentation: dev-manual - Edits to setup part of example
Minor edits to the part of the example that sets up for the
first core-image-minimal build. Put in the variable to use
for the build environment setup script, updated some changed
output from some of the commands, etc.
Scott Rifenbark [Thu, 4 Oct 2012 15:38:11 +0000 (08:38 -0700)]
documentation: Makefile, dev-manual - Updated kernel example repo figure
Danny, the "kernel-example-repo-<release>.png" file changed to
"kernel-example-repo-danny.png". To correctly make the dev-manual
and the mega-manual some things needed to change:
1. New figure created and added to both the dev-manual and the
mega-manuals figures directory.
2. The "kernel-example-repo-denzil.png" files from the dev-manual
and mega-manual figures directory was removed.
3. The Makefile was adjusted so a new BRANCH=danny area now exists
to set TARFILES for both dev-manual and mega-manual.
Saul Wold [Fri, 5 Oct 2012 23:59:03 +0000 (16:59 -0700)]
pulseaudio: ensure X11 and consolekit are disabled
When DISTRO_FEATURES does not include X11 ensure that both x11
and gtk are diabled correctly. ConsoleKit also has x11, so ensure
that any RDEPENDS is also excluded.
The flags for x11 changed at somepoint to use enable/disable, but
this recipe was not updated.
Mark Hatle [Fri, 5 Oct 2012 18:21:51 +0000 (11:21 -0700)]
package_rpm.bbclass: Fix an issue where complementary installs fail
Also ensure that we always cleanup the temporary install manifest files,
some of them will cause problems if they exist in multiple install
attempts.
Finally verify that the lists remain uniquely sorted otherwise the
complementary install may install the same files numerous times,
triggering a failure.
Richard Purdie [Fri, 5 Oct 2012 13:13:13 +0000 (13:13 +0000)]
sstate: Add extra entries to the sstate duplicate files whitelist
This avoids errors where gcc/binutils get installed to the native sysroot
in the same location for multiple package architectures. Ultimately making
these native recipes with ${PACKAGE_ARCH} appended to PN will resolve this
but hide the warnings until this gets sorted out.
Also hide the python and docbook catalog warnings since they're known about,
nothing to worry about and we'll aim to clean them up properly in the 1.4 cycle.
Richard Purdie [Fri, 5 Oct 2012 11:46:05 +0000 (11:46 +0000)]
libdrm: Explicitly disable the cairo dependency
We don't want the cairo dependency. Unfortunately simply checking whether its present
isn't good enough. If its not in DEPENDS, it can disappear half way through building.
We therefore need to explictly disable it.
Khem Raj [Thu, 4 Oct 2012 23:47:39 +0000 (16:47 -0700)]
toolchain-scripts.bbclass: Export M4
some packages use M4 variable from environment and sometimes
its hardcoded to /usr/bin/m4 if not found in environment. Lets
define it such that it is picked from path
Scott Garman [Wed, 3 Oct 2012 22:13:53 +0000 (15:13 -0700)]
runqemu: allow multiple unfs instances to run simultaneously
A miscalculation in the way the port numbers of mountd and nfsd
are created was causing conflicts when starting multiple instances
of qemu using userspace nfs.
mountd requires rpcbind or portmap. Check that one of these
services is running before doing anything else, and report
a user-friendly error when they are not found.
Removing the Appendix A (BSP) example had some rippling affects
throughout the doc set. There were several links into the appendix.
All these links had to either be modified (if possible) or simply
removed since the appendix will be removed.
This section now points into the BSP Guide where it talks
about using the yocto-bsp script to create a BSP. The prior
method was by hand and described in an appendix (A) of the
YP Development Manual.
FYI - this results in the removal of Appendex A in a future
commit.
Scott Rifenbark [Wed, 3 Oct 2012 20:04:23 +0000 (13:04 -0700)]
documentation: poky-ref-manual, yocto-project-qs - Updates to packages
A few edits to the respective sections that talk about required
packages. Some wording changes for headless and graphics
supported systems. Also, re-inserted the note about older
CentOS systems.
Scott Rifenbark [Wed, 3 Oct 2012 16:01:12 +0000 (09:01 -0700)]
documentation: bsp-guide - scrub edits for the BSP Tools section
I did a walk through of the "Using the Yocto Project's BSP Tools"
section. Updated included altered output based on the current
example commands and scenarios.
Also made changes to the bblayers.conf file as the default
version for this file has changed.
Scott Rifenbark [Wed, 3 Oct 2012 15:37:45 +0000 (08:37 -0700)]
documentation: dev-manual - Updated Enabling Your Layer section
This section was out of date. I copied in the most recent version
of the bblayers.conf file, which sets LCONF_VERSION to "6" now.
Also, added the meta-yocto-bsp layer to the example.
Additionally, I inserted a Note explaining the consequences of
removing the meta-yocto layer. The note references [YOCTO_#3176]
for more information.
Reorganization of the packages section in the YP Quick Start.
These are now ordered still by distro but the listed packages
have been culled down to just the needed ones to run an
image on QEMU with graphical support.
A corresponding section in the reference manual now provides
the comprehensive list of packages for all supported distros.
The section in the reference manual is broken down by
distro and by function.
Finally, four new variables were introduced to track the
essential packages for each of the distros. The variables
are defined in poky.ent and follow the form
<distro>_HOST_PACKAGES_ESSENTIAL. This will make it so
we don't have to maintain this list of essential packages
in multiple places.
Ross Burton [Thu, 4 Oct 2012 11:19:03 +0000 (12:19 +0100)]
sato-icon-theme: use gtk-icon-cache helper class
Instead of explicitly updating the icon cache use the helper class that also
forces a loader update at the same time. This eliminates the possibility of
updating the icon cache without any gdk-pixbuf loaders.
Also check that the Sato icon theme isn't already set to avoid appending to the
file every time the postinst runs.
Saul Wold [Wed, 3 Oct 2012 16:33:16 +0000 (09:33 -0700)]
distrodata: Update distrocheck functions
Fix the distro check functions for the change of nativesdk
being a suffix to a prefix. Also added crosssdk as another
case for converting to PN for matching in the distro_tracking
bitbake: hob/image_details/run_image: Kernel must be set
- when displaying image details, even if the kernel information is not shown, the kernel value must be set (if dealing with qemu) otherwise running the image will throw an error
(Bitbake rev: 334125a98ecb8a938aee4bc530205ad75099361c)
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Wed, 3 Oct 2012 12:27:57 +0000 (13:27 +0100)]
bitbake: fetch2: raise an exception if user specifies protocol=git with http://
It is a common mistake to use http:// and protocol=git when attempting
to fetch from a git repository using the http protocol; if this is
detected then throw an error explaining that you need to use git:// with
protocol=http instead.
Paul Eggleton [Wed, 3 Oct 2012 12:37:16 +0000 (13:37 +0100)]
rpmresolve: fix reporting of multiple matches error
We were mistakenly writing what was meant to go to stderr into the
output file, so when the "Multiple matches" error showed we weren't
actually seeing the matches printed.
Also change the wording of the "Unable to find package..." to "Unable
to resolve package..." instead so that it makes more sense if it is
printed after the "Multiple matches" error.
Cristian Iorga [Wed, 3 Oct 2012 12:18:58 +0000 (15:18 +0300)]
qemu: Fixed running QEMU with virtio error reporting
If vhost_net module is not properly installed,
runqemu script will report the error and
provide the user with a link to the guide.
Also corrected small cosmetic issues in
runqemu script messages.
Also removed <> (read/write) check.
Ross Burton [Wed, 3 Oct 2012 12:12:18 +0000 (13:12 +0100)]
wpa-supplicant: don't break the DBus service file
The recipe exports $BINDIR as ${sbindir} and the build system uses this when
writing the DBus service file, so sedding it and replacing $base_sbindir with
$sbindir (/sbin and /usr/sbin) isn't useful when it ends up as
/usr/usr/sbin/wpa_supplicant.
For some reason the code calls int() on the epoch component of any
PREFERRED_VERSION. Since this is compared against strings, the comparison
would always fail. This removes the stray cast and allows epochs
in preferred_version to work correctly.
Laurentiu Palcu [Wed, 3 Oct 2012 11:23:26 +0000 (14:23 +0300)]
qemu: add wrapper for qemu-mips binary
qemu-mips user emulation binary segfaults when running any kind of
binary. This is due to a MMU access fault in the virtual CPU. This
problem has been introduced in qemu when 4GB of vmem were reserved for
32-on-64 bit.
This workaround will need to be reverted once the proper fix is found.
Phil Blundell [Tue, 2 Oct 2012 17:16:24 +0000 (18:16 +0100)]
e2fsprogs: Don't install findfs
This binary is provided by util-linux nowadays. Fixes:
WARNING: The recipe is trying to install files into a shared area when those files already exist. Those files are:
/fast/jenkins/workspace/.../tmp-eglibc/sysroots/x86_64-linux/sbin/findfs
The license for bzip2 is not quite BSD. I have an email out to the
maintainer to see if we can utilize a common BSD license (or something
else) however, for now, we should revert bzip2 back to a special
license.
As busybox also utilizes a lightly modified bzip2, this also
effects busybox.
Darren Hart [Wed, 3 Oct 2012 04:36:41 +0000 (21:36 -0700)]
linux-yocto-custom: Clarify defconfig usage
It is necessary to supply file://defconfig to the SRC_URI when using
a defconfig (it is not implicitly understood as the commentary might
currently suggest).
Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Wed, 3 Oct 2012 08:58:24 +0000 (09:58 +0100)]
package.bbclass: Fix regression in -dbg packages introduced by explode_dep_versions change
We need to iterate over the dictionary pulling out the values, not take the top
level keys. If we don't do this, we end up with dependencies on the values of
PACKAGES, not library dependencies.
Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The git proxy check seems to be hurting the user experience more than
its helping it so lets remove it andonly check http/https. Most builds
should be able to work from the http:// urls from the mirrors.
This also brings some parity to the situation as svn:// were not being
checked.
Paul Eggleton [Tue, 2 Oct 2012 16:24:47 +0000 (09:24 -0700)]
documentation: poky-ref-manual - Updates to faq entry
Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently. The faq entry changed is
"How does Poky differ from OpenEmbedded?"
Paul Eggleton [Tue, 2 Oct 2012 16:18:59 +0000 (09:18 -0700)]
documentation: poky-ref-manual - Wording change for faq entry.
The entry for the question "Are there any products using
the OpenEmbedded build system (poky)?" was updated. The
changes result in a better question and answer.
Paul Eggleton [Tue, 2 Oct 2012 16:13:30 +0000 (09:13 -0700)]
documentation: poky-ref-manual, dev-manual - added link to oe-core
* Explain that we test with a set of reference hardware rather than only
supporting hardware that we have (avoiding any implication that the
build system can't support other devices). These are in the
faq entry in the poky-ref-manual for the question of how we can
claim Poky / OpenEmbedded-Core is stable.
* Adjust the language so that it is OE-Core friendly, with a link to
the Development Manual for the definition of OE-Core.