ping
On 10/21/2014 02:30 PM, Chen Qi wrote:
The following changes since commit fcbd1b19383daf5e160a864df1418130da01be28:
build-appliance-image: Update to dizzy head revision (2014-10-11 08:11:11
+0100)
are available in the git repository at:
ping
On 12/10/2014 01:43 PM, Chong Lu wrote:
Change since V2:
don't change SERIAL_CONSOLE default value and add console.bbclass to get
port, tty and baud rate from SERIAL_CONSOLE.
The following changes since commit ec6377bcf52d105cd23ac6bbbeddd38fee9337e4:
bitbake:
Ping.
-Original Message-
From: Chunrong Guo [mailto:b40...@freescale.com]
Sent: Thursday, December 11, 2014 11:33 AM
To: openembedded-core@lists.openembedded.org
Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Guo
Chunrong-B40290
Subject: [OE-core][PATCH v4 1/2]
The following changes since commit 8d0e56a850579f9a6d501266deeef9b257ce4780:
serf: readded md5sum (2014-12-11 11:34:22 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/lsb
The sysroot/${libdir}/sendmail conflicts with esmtp's, and it's a
symlink to ${sbindir}/sendmail which is meaningless for sysroot, so
remove it.
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta/recipes-extended/lsb/lsb_4.1.bb |8
1 file changed, 8 insertions(+)
diff
Fix to use ${nonarch_base_libdir}/udev/rules.d instead of */udev/rules.d
to avoid the following QA warning.
ERROR: QA Issue: alsa-utils: Files/directories were installed but not shipped
/usr/lib/udev
/usr/lib/udev/rules.d
/usr/lib/udev/rules.d/90-alsa-restore.rules [installed-vs-shipped]
Instead of using paths like '/etc' and '/bin', we should use ${sysconfdir}
and ${base_bindir}.
Otherwise, when ${base_bindir} is not '/bin', there would be errors.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/recipes-core/busybox/busybox.inc | 66 +--
1
This patchset mainly fixes several hardcoding problems.
There's a bug in Yocto's bugzilla:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7040
Bug 7040 - Support for /usr merge (à la systemd and Fedora)
I did some investigation and made it work for core-image-sato-sdk.
The solution is
Instead of using '/lib', we should use ${nonarch_lib_dir}.
Otherwise, when ${nonarch_lib_dir} is not /lib, there would be errors.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/recipes-core/systemd/systemd_216.bb | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff
It's possible that ${base_bindir} and ${bindir} point to the same directory.
So we need to test it before moving things around or removing things.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/recipes-extended/sed/sed_4.1.2.bb | 6 --
meta/recipes-extended/sed/sed_4.2.2.bb | 6 --
FILES_${PN}-utils = ${bindir}/* ${sbindir}/*
FILES_${PN} = ${libc_baselibs} ${libexecdir}/*
${@base_conditional('USE_LDCONFIG', '1', '${base_sbindir}/ldconfig
${sysconfdir}/ld.so.conf', '', d)}
From the above two assignments, we can see that ${PN}-utils needs to be ordered
after ${PN} in the
I want to give people a headsup that we're having problems merging
changes at the moment. We've been doing our best but the number of
things building up which are causing issues is overwheling our ability
to fix and stablise the build. It wasn't helped that I took a long
weekend's vacation last
Bruce Ashfield bruce.ashfield-cwa4wttnnzf54taoqty...@public.gmane.org
writes:
With the kernel build optimizations, we no longer copy the source from
the built kernel into the staging dir, since the kernel is unpacked and built
directly from the staging dir.
This means that a few build
I've been looking at how to make it easier for application and system
component developers to get their work done using the tools we provide,
and I believe this patchset is a piece of the solution. There's still a
number of other pieces to come, but this should be usable on its own.
The first
This allows us to use this function elsewhere in the code.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/classes/package.bbclass | 24 +---
meta/lib/oe/package.py | 26 ++
2 files changed, 27 insertions(+), 23 deletions(-)
With siggen being changed to alter the signature of nostamp tasks on the
fly, having these tasks as nostamp results in the SDK being rebuilt
every time, which is not desirable. In any case this is just legacy from
the days before we used signatures to take care of ensuring these tasks
get re-run
When PATCHTOOL = git, git apply doesn't support fuzzy application, so
if a patch requires that it's better to be able to apply it rather than
just failing.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/lib/oe/patch.py | 6 +-
1 file changed, 5 insertions(+), 1
When PATCHTOOL = git, if we're not able to use git am to apply a
patch and fall back to git apply or patch, it is desirable to
actually commit the changes, attempting to preserve (and interpret) the
patch header as part of the commit message if present. As a bonus, the
code for extracting the
If we don't do this, you may still be in the git am resolution mode at
the end of applying patches, which is not desirable.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/lib/oe/patch.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/lib/oe/patch.py
When patches from a recipe have been written out to a git tree, we also
want to be able to do the reverse so we can update the patches next to
the recipe. This is implemented by adding a comment to each commit
message (using git hooks) which we can extract later on.
Signed-off-by: Paul Eggleton
Add a more maintainable and flexible script for creating at least the
skeleton of a recipe based on an examination of the source tree.
Commands can be added and the creation process can be extended through
plugins.
[YOCTO #6406]
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
* Enable querying exported variables
* Use strip() to remove quotes so any internal quotes are not disturbed
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/lib/oeqa/utils/commands.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Preserving carriage returns is important where the patch contains them.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/lib/oe/patch.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oe/patch.py b/meta/lib/oe/patch.py
index 2d56ba4..2bf3065
Most of the time what you want when using this class is for do_compile
to execute more than just once - every time the source changes would be
ideal, but that's a little tricky to accomplish. Thus, set do_compile as
nostamp to get something close. Note that in order to be effective this
also
From: Junchun Guan junchunx.g...@intel.com
Deploy recipe output files to live target machine using scp
Store the files list and target machine info in localhost if deployment
is done
Undeploy recipe output files in target machine using the previous
deployment info
[YOCTO #6654]
Signed-off-by:
Provides an easy means to work on developing applications and system
components with the build system.
For example to modify the source for an existing recipe:
$ devtool modify -x pango /home/projects/pango
Parsing recipes..done.
NOTE: Fetching pango...
NOTE: Unpacking...
NOTE:
Add a module to help provide utility functions for dealing with recipes.
This would typically be used by external tools.
Substantial portions of this module were borrowed from the OE Layer
index code; other functions originally contributed by
Markus Lehtonen markus.lehto...@intel.com.
Add a utility module for scripts. This is intended to provide functions
only really useful before bitbake has been found (or only of particular
interest to scripts). At the moment this includes functions for setting
up a logger and for loading plugins.
Signed-off-by: Paul Eggleton
Add some QA tests for devtool (and recipetool). These aren't
comprehensive but at least they are a start, and have already helped me
catch and fix a number of regressions.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/lib/oeqa/selftest/devtool.py | 239
On Fri, 2014-12-19 at 12:05 +0100, Enrico Scholz wrote:
Bruce Ashfield bruce.ashfield-cwa4wttnnzf54taoqty...@public.gmane.org
writes:
With the kernel build optimizations, we no longer copy the source from
the built kernel into the staging dir, since the kernel is unpacked and
built
Richard Purdie richard.pur...@linuxfoundation.org writes:
In our usecase we build usually two kernels: a full featured one for
the main system and a minimal, initramfs based for a rescue system.
With this change and building both kernels, it is ambiguous which
System.map is used.
On Fri, 2014-12-19 at 13:11 +0100, Enrico Scholz wrote:
Richard Purdie richard.pur...@linuxfoundation.org writes:
to the point of not being a currently well supported use case and the
classes would probably need to be refactored to allow such things to
be well supported. These changes do
On Fri, 2014-12-19 at 10:28 +, Richard Purdie wrote:
I want to give people a headsup that we're having problems merging
changes at the moment. We've been doing our best but the number of
things building up which are causing issues is overwheling our ability
to fix and stablise the build.
On 2014-12-19, 7:41 AM, Richard Purdie wrote:
On Fri, 2014-12-19 at 10:28 +, Richard Purdie wrote:
I want to give people a headsup that we're having problems merging
changes at the moment. We've been doing our best but the number of
things building up which are causing issues is overwheling
On Fri, Dec 19, 2014 at 8:07 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 2014-12-19, 7:41 AM, Richard Purdie wrote:
On Fri, 2014-12-19 at 10:28 +, Richard Purdie wrote:
I want to give people a headsup that we're having problems merging
changes at the moment. We've been
On Fri, 2014-12-19 at 08:07 -0500, Bruce Ashfield wrote:
On 2014-12-19, 7:41 AM, Richard Purdie wrote:
On Fri, 2014-12-19 at 10:28 +, Richard Purdie wrote:
I want to give people a headsup that we're having problems merging
changes at the moment. We've been doing our best but the number
In particular this removes a race condition where a ${S}/patches
directory could be created by do_unpack. This confuses kern-tools.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
diff --git a/meta/classes/kernelsrc.bbclass b/meta/classes/kernelsrc.bbclass
index 11f04e9..4208eff
On Fri, Dec 19, 2014 at 8:15 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Fri, 2014-12-19 at 08:07 -0500, Bruce Ashfield wrote:
On 2014-12-19, 7:41 AM, Richard Purdie wrote:
On Fri, 2014-12-19 at 10:28 +, Richard Purdie wrote:
I want to give people a headsup that we're
As a normal recipe, mulitlib would try and extend it for multilibs.
By inheriting module-base, we can avoid this since we now look more
'kernel' like.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb
On 14-12-19 08:18 AM, Richard Purdie wrote:
In particular this removes a race condition where a ${S}/patches
directory could be created by do_unpack. This confuses kern-tools.
Looks good here. This will keep the dreaded 'patches' directory from
popping up and mucking up the existing detection
On 14-12-19 09:12 AM, Richard Purdie wrote:
As a normal recipe, mulitlib would try and extend it for multilibs.
By inheriting module-base, we can avoid this since we now look more
'kernel' like.
Also looks good. I didn't trigger the multilib issues here, but looking
at the arch settings in
After the recent kernel changes, non linux-yocto builds stopped working
properly for two reasons:
a) ${S} was being reset to ${WORKDIR}/git for example and STAGING_KERNEL_DIR
did not contain the source
b) Most builds were using ${B} == ${S}
This patch adds a fixup to the unpack function to
bzImage is no longer in STAGING_KERNEL_DIR. Rather than add it back,
depend on the kernel deploy task and find it in DEPLOY_DIR_IMAGE.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index 8a305af..003816b
On 2014-12-19 10:46, Richard Purdie wrote:
After the recent kernel changes, non linux-yocto builds stopped working
properly for two reasons:
a) ${S} was being reset to ${WORKDIR}/git for example and STAGING_KERNEL_DIR
did not contain the source
b) Most builds were using ${B} == ${S}
This
font-util installs encoding maps into /usr/share/fonts/X11. This path
may not exist on the host (many distros install these into
/usr/share/fonts/util) so they must exist in the sysroot in order for
e.g. `pkg-config --variable=mapdir fontutil` to work correctly. However,
currently /usr/share/fonts
The xorg font builds use `pkg-config --variable=mapdir fontutil` to
locate encoding maps. This variable ought to be sysroot-relative, but
neither pkg-config nor font-util nor the fonts themselves provide any
facility to add the sysroot back in.
We're presently adding the sysroot by by twiddling
(This is just a rebase; no changes vs v1.)
Several xorg-font builds were added to meta-oe recently. These builds tend to
fail on several Linux distros because they referenced encoding maps (e.g.
map-ISO8859-1) at native paths outside the sysroot, which don't exist; the build
expects
MAPFILES_PATH is a configuration variable that is used by packages using
font-util, which tells those packages how to compute it in fontutil.m4.
Presently, we're manually twiddling things so that MAPFILES_PATH will
consult the native sysroot, when building under *any* architecture.
This
Drop removal of [|()*] operators in pkged_lic because this removal is only
needed to validate if license is collected.
[YOCTO #6757]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
meta/classes/license.bbclass | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
49 matches
Mail list logo
