On 11/24/2014 07:26 PM, Burton, Ross wrote:
On 24 November 2014 at 05:19, Chong Lu chong...@windriver.com
mailto:chong...@windriver.com wrote:
After I upgrade bison, I test world on qemuppc and qemux86, that's ok.
Can you tell me, which arch will build failure or how to reproduce
resolvconf was missing a script and needed readlink which was in
/usr/bin. Also the /etc/resolv.conf was not being correctly linked
to /etc/resolvconf/run/resolv.conf, which is fixed by the volaties
change which is now a file as opposed to created in do_install.
Ensure that the correct
Changelog since 2014-11-16 until 2014-11-23. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
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
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
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
---
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.
[Note: this is an RFC series for the moment, and shouldn't yet be merged.]
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
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
Provides an easy means to work on developing applications and system
components with the build system.
You can start by creating a workspace layer (only needs to be done
once):
$ devtool create-workspace
Then you can use the other functions, for example to modify the source
for an existing
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:
On 25 November 2014 at 17:28, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
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
On 25 November 2014 at 17:28, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
[Note: this is an RFC series for the moment, and shouldn't yet be merged.]
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
Hi Paul,
On Tuesday 25 November 2014 17:40:24 Paul Barker wrote:
On 25 November 2014 at 17:28, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
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
The current implementation of shared work for gcc is at best confusing. It
relies
on the fetch/unpack/patch tasks having exactly the same stamps and if this gets
broken for some reason, its hard to figure out what the problem is. It also
leads to complex code in bitbake.
The benefits of shared
The v2.7 release of powertop fixes devfreq support for ARM, along with
other bug fixes.
Signed-off-by: Ezra Savard ezra.sav...@xilinx.com
---
meta/recipes-kernel/powertop/powertop_2.7.bb | 31
1 file changed, 31 insertions(+)
create mode 100644
On Tuesday 25 November 2014 17:51:05 Paul Barker wrote:
On 25 November 2014 at 17:28, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
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
Adding Armin (for dizzy).
On Tue, 2014-11-04 at 22:11 -0500, Bruce Ashfield wrote:
On 2014-11-04, 6:58 PM, Kamble, Nitin A wrote:
-Original Message-
From: Zanussi, Tom
Sent: Tuesday, November 04, 2014 3:26 PM
To: Kamble, Nitin A
Cc: richard.pur...@linuxfoundation.org; Wold,
Wow, this is exciting!
Just thinking out loud here... is there a way to way to have the
devshell come up without having applied any patches but with the patches
already queued in, say, a quilt series?
It seems to happen often enough to me that: a recipe has 10 local
patches which applied fine
Hi all,
Does anyone know why the configuration files for opkg are split into
opkg-config-base (containing just '/etc/opkg/arch.conf') and
opkg-collateral (containing just '/etc/opkg/opkg.conf')? It looks like
the split dates back to openembedded classic.
If there isn't a good reason for this
On 25 November 2014 at 17:52, Ezra Savard ezra.sav...@xilinx.com wrote:
meta/recipes-kernel/powertop/powertop_2.7.bb | 31
Please also delete 2.6.1.
Ross
--
___
Openembedded-core mailing list
Hi George,
This patch got totally mangled - can you resend it (or push to a repo)?
Ross
On 19 November 2014 at 07:43, Musat, George L george.l.mu...@intel.com
wrote:
Removed Poky-1.4, Poky-1.5, Ubuntu-13.10, Fedora-19,
CentOs-6.4,Suse-LINUX-12.2. Replaced the list of Debian-7.x with
On 21 November 2014 at 09:17, Jian Liu jian@windriver.com wrote:
+CONFFILES_${PN} += ${localstatedir}/lib/logrotate.status
Why does this need to be marked as a conf file, and if it's because it's
per-machine state why is it included in the package?
Ross
--
On 21 November 2014 at 09:17, Jian Liu jian@windriver.com wrote:
Use CONFFILES to mark editable files as such,
/var/lib/nfs/etab
/var/lib/nfs/statd/state
/var/lib/nfs/rmtab
Again, why is state being shipped in a package?
Ross
--
___
24 matches
Mail list logo
