From: Chen Qi qi.c...@windriver.com
/etc/udev/scripts/mount.sh is removed by init-install.sh, but the udev
rules file which specifies the invocation of this script is not removed,
thus causing the error message '/etc/udev/scripts/mount.sh: No such file
or directory' shown at a live install.
The
From: Chen Qi qi.c...@windriver.com
The following changes since commit 3c5f4d54d01887a117bf659fc9af6b2b892c2b08:
separatebuilddir.inc: mxsldr should never have been added to this list,
remove (2013-03-24 14:03:19 +)
are available in the git repository at:
This can cause issues building ppc64/eabi kernel. For details
see the patch header
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta/recipes-devtools/binutils/binutils-2.23.1.inc |1 +
...pc.c-md_assemble-Do-not-generate-APUinfo-.patch | 46
2 files changed, 47
V2:
Update commit comments
The following changes since commit f36926a264190e6202830e8520b41b30ae77ea43:
docbook-utils-native: Unbreak the build after source and build dir split
(2013-03-25 20:51:19 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib
This bug occurs on rpm-based sdk image.
update-alternatives-cworth is default installed into sato image. And for
sato-sdk image, it installs every related dev packages.
update-alternatives-cworth is from opkg, so opkg-dev is installed and it
requires opkg, then opkg is installed into sato-sdk
From: Chen Qi qi.c...@windriver.com
The following changes since commit 3c5f4d54d01887a117bf659fc9af6b2b892c2b08:
separatebuilddir.inc: mxsldr should never have been added to this list,
remove (2013-03-24 14:03:19 +)
are available in the git repository at:
From: Chen Qi qi.c...@windriver.com
This script is intended to start at runlevel 2 3 4 5, as specified
in its HEAD INFO area.
The fact that it was not started at runlevel 3 caused splash screen
not going away when booting into runlevel 3.
[YOCTO #3904]
Signed-off-by: Chen Qi
Am 26.03.2013 06:55, schrieb Khem Raj:
On Mar 12, 2013, at 7:49 AM, Stefan Herbrechtsmeier
ste...@herbrechtsmeier.net wrote:
The current boost recipe only creates the bjam build tool during
a native run and thereby is not usable for other native recipes
that depend on a boost library. Use
From: Anders Roxell anders.rox...@enea.com
Log:
/etc/rcS.d/S37populate-volatile.sh: line 13: sed: command not found
/etc/rcS.d/S37populate-volatile.sh: line 152: sed: command not found
/etc/rcS.d/S37populate-volatile.sh: line 152: sed: command not found
Signed-off-by: Anders Roxell
Hello all,
I will test today an install path for bluez5 using the opkg manager in a
existent image.
I will keep you updated.
Regards,
Cristian
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
On 25 March 2013 23:47, Andreas Müller schnitzelt...@googlemail.com wrote:
fixes:
| ERROR: Multiple .bb files are due to be built which each provide
virtual/gtk-update-icon-cache-native
|
On Mon, 2013-03-25 at 16:47 -0500, Mark Hatle wrote:
I've looked at the code some more. It does checksum the header itself and
then
if it's got contents, it also adds the contents to the checksum.. That is
where
the failure appears to be happening:
if (u.shdr.sh_type !=
On Tue, Mar 26, 2013 at 11:32 AM, Burton, Ross ross.bur...@intel.com wrote:
On 25 March 2013 23:47, Andreas Müller schnitzelt...@googlemail.com wrote:
fixes:
| ERROR: Multiple .bb files are due to be built which each provide
virtual/gtk-update-icon-cache-native
|
On Tue, 2013-03-26 at 12:40 +0100, Andreas Müller wrote:
On Tue, Mar 26, 2013 at 11:32 AM, Burton, Ross ross.bur...@intel.com wrote:
On 25 March 2013 23:47, Andreas Müller schnitzelt...@googlemail.com wrote:
fixes:
| ERROR: Multiple .bb files are due to be built which each provide
On 3/26/13 5:38 AM, Phil Blundell wrote:
On Mon, 2013-03-25 at 16:47 -0500, Mark Hatle wrote:
I've looked at the code some more. It does checksum the header itself and then
if it's got contents, it also adds the contents to the checksum.. That is where
the failure appears to be happening:
A couple of fixes to hopefully help us track down the qemuimagetest
failures on the autobuilder.
The following changes since commit d60aec3f5b319f4583fa72a8357b9ddd3be62b1a:
docbook-utils-native: Unbreak the build after source and build dir split
(2013-03-25 20:51:15 +)
are available in
The helper script was printing an error to stdout when it couldn't find
any qemu child processes; output this error to stderr instead and
redirect stderr to /dev/null when running from qemuimage-testlib so that
QEMUPID is actually blank if there are no qemu instances found.
Signed-off-by: Paul
If runqemu (or qemu itself) fails we need to know why, so tee out to a
log file and print it when we can't find the qemu process or determine
its IP address.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/classes/imagetest-qemu.bbclass |1 +
scripts/qemuimage-testlib
The current boost recipe only creates the bjam build tool during
a native run and thereby is not usable for other native recipes
that depend on a boost library. Split out the build tool into its
own bjam-native recipe and add real native support to the boost
recipe. Additionally replace the
When I build nativesdk toolchain with recent poky + meta-fsl-ppc + FSL SDK
specific layers, build issue similar to error-1 happens. This issue might
appear for different gcc related package during different trial, e.g. libgcc,
gcc, gcc-cross-initial, gcc-crosssdk, etc.
When I revert
Updating the base v3.8 kernel to the 3.8.4 -stable version.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
Richard,
Here's a consolidated pull request that I've been working on last
week, and more intensively since tglx dropped the 3.8-rt release
late last week.
This series is a collection of kernel fixes:
[linux-yocto/3.8: fix perf host contamination]
Usability tweaks:
[linux-yocto/3.8: allow
Bumping the kern-tools SRCREV to pickup the following fixes and documentation
updates:
d484e3f kgit-meta: remove hardcoded meta directory name
affad20 yocto-kernel-tools: Typoes, fragement, depreciated
142ed49 kgit-init: update tools list
Signed-off-by: Bruce Ashfield
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be prevented in a layer without using python code and
a recipe finalize hook.
To allow easier overriding of 'extra' or 'optional' features that
Updating the 3.4 tree to import the korg -stable fixes for v3.4.36.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |8
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb |6 +++---
On Tue, 2013-03-26 at 14:29 +, Luo Zhenhua-B19537 wrote:
When I build nativesdk toolchain with recent poky + meta-fsl-ppc + FSL SDK
specific layers, build issue similar to error-1 happens. This issue might
appear for different gcc related package during different trial, e.g. libgcc,
On 03/26/2013 07:46 AM, Bruce Ashfield wrote:
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be prevented in a layer without using python code and
a recipe finalize hook.
To allow easier
On 13-03-26 11:48 AM, Darren Hart wrote:
On 03/26/2013 07:46 AM, Bruce Ashfield wrote:
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be prevented in a layer without using python code and
a
On 03/26/2013 08:49 AM, Bruce Ashfield wrote:
On 13-03-26 11:48 AM, Darren Hart wrote:
On 03/26/2013 07:46 AM, Bruce Ashfield wrote:
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be
Earlier commits bumped the upstream version, but we need to update
our copy of the pkg-config file too.
(It'd probably be better to generate this at build time, otherwise
this will be a trap people continually fall into)
Signed-off-by: Colin Walters walt...@verbum.org
---
Hello all,
Initial status:
QEmu machine core-image-sato.
Follow the /update/upgrade/install path as below:
Fact: bluez5, at this point, is not an upgrade path for bluez4.
Logical conclusion would be that bluez 5 and bluez4 should be provided only
with RCONFLICTS (case 2), so that doing an:
Add bash runtime dependence, required at package install time.
Signed-off-by: Giuseppe Condorelli giuseppe.condore...@st.com
---
meta/recipes-connectivity/iproute2/iproute2.inc|1 +
.../iproute2/iproute2_3.8.0.bb |2 +-
2 files changed, 2 insertions(+), 1
From: Nitin A Kamble nitin.a.kam...@intel.com
Due to recent changes in the oecore layer to use separate builddir, the
grub-efi-native recipe need to change to avoid build errors.
Thanks,
Nitin
The following changes since commit c376f1f49cea182a2887945840ab97a20970a373:
package.bbclass:
From: Nitin A Kamble nitin.a.kam...@intel.com
Due to recent change in the oecore layer grub-efi recipe uses separate
builddir and the paths used in the do_deply need to change accordingly.
This change avoids this build issue:
install: cannot stat
Compressed journals means using liblzma, sf the journal isn't going to be used
this can be disabled.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd_197.bb |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Hi,
An iteration on the previous series, this fixes the issues that Saul and Martin
noticed, removes the commit that is targetted at meta-yocto, and importantly
fixes pure-systemd booting which was previously aborting dramatically when
populate-volatiles copied the contents of /run to
systemd uses strictatime when mounting tmpfs. Luckily this is already supported
upstream, so backport the patch from git.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
.../busybox/busybox-1.20.2/strict-atime.patch | 49
systemd ships its own databases (hwdb), so we don't need another copy.
--with-pci-ids isn't recognised by configure, so remove it.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd_197.bb |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
This uses BAD_RECOMMENDATIONS which isn't supported by all package backends, but
it's a start.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/images/core-image-minimal-initramfs.bb |2 ++
1 file changed, 2 insertions(+)
diff --git
From: Radu Moisan radu.moi...@intel.com
Signed-off-by: Radu Moisan radu.moi...@intel.com
Signed-off-by: Andreas Müller schnitzelt...@googlemail.com
Signed-off-by: Khem Raj raj.k...@gmail.com
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
Signed-off-by: Ross Burton ross.bur...@intel.com
---
Merge the contents of udev-systemd, which is just the service files, into udev
itself. This split wasn't intended to ever happen in oe-core.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd_197.bb |9 -
1 file changed, 4 insertions(+), 5
Change the logic so that the udev provider is the standalone udev, unless the
systemd DISTRO_FEATURE is set. The previous logic was designed to fail if both
sysvinit and systemd were enabled, which we're supporting now.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
The hardware databases are not essential and also quite large, so split them out
into udev-hwdb.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd_197.bb | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git
Run the helper if the sysvinit feature is present, or if the systemd feature is
present but the systemd class hasn't been inherited. We want to run in the
latter case as systemd has sysvinit compatibility, but we don't want to always
run so that pure systemd images don't have redundant sysvinit
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/classes/update-rc.d.bbclass | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/classes/update-rc.d.bbclass b/meta/classes/update-rc.d.bbclass
index 06b91c1..0997702 100644
---
With both sysvinit and systemd features enabled these postinsts may actually run
on a target without systemd, so check that systemctl is present before using it.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/classes/systemd.bbclass | 27 +++
1 file changed,
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/util-linux/util-linux.inc | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/util-linux/util-linux.inc
b/meta/recipes-core/util-linux/util-linux.inc
index 41a5471..46daab7
DISTRO_FEATURES_INITMAN is going away as it's not useful in a hybrid init script
environment.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/conf/distro/include/default-distrovars.inc |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Rename SYSTEMD_BBCLASS_ENABLED to INHIBIT_UPDATERCD_BBCLASS to reflect the
action, for clarity.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/classes/systemd.bbclass | 11 +++
meta/classes/update-rc.d.bbclass |8 +++-
2 files changed, 10 insertions(+), 9
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/conf/distro/include/default-distrovars.inc |1 -
1 file changed, 1 deletion(-)
diff --git a/meta/conf/distro/include/default-distrovars.inc
b/meta/conf/distro/include/default-distrovars.inc
index eafbcc2..b0586d6 100644
---
With both sysvinit and systemd features it's possible to use systemd's udev with
sysvinit, so add the required init script.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd/init | 101 ++
Reflect reality by backfilling sysvinit support, instead of whatever value was
in DISTRO_FEATURES_INITMAN.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/conf/bitbake.conf |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf
Don't follow DISTRO_FEATURES_INITMAN as that makes the packagegroups rebuild if
you switch init manager.
As in hybrid situations there's generally a clear primary and minimal init
manager choice, so change VIRTUAL-RUNTIME_init_manager to set the primary init
manager, and roll your own
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/busybox/busybox.inc |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/busybox/busybox.inc
b/meta/recipes-core/busybox/busybox.inc
index e936e59..655cb3c 100644
---
From: Andreas Oberritter o...@opendreambox.org
For hybrid systemd/sysvinit builds, only one fstab can be used.
The default fstab used by sysvinit should work fine with systemd.
Since virtually every machine will ship its own fstab in its bsp
layer, the bsp layer may decide how to override the
If systemd isn't a distro feature, explicitly disable the systemd unit path
check as otherwise it will search the sysroot.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/dbus/dbus.inc |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
initscripts is generally installed on systemd-using images, but because it
specifies that /run is a symlink to /var/run managed by volatiles it totally
breaks systemd by copying/deleting /run from underneath systemd. Deleting
sockets mid-boot doesn't leave systemd in a happy place.
As this
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd-compat-units.bb |1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/systemd/systemd-compat-units.bb
b/meta/recipes-core/systemd/systemd-compat-units.bb
index 19a1ea1..9b4a8a4 100644
---
These are more than useful as they ensure some services are not started twice,
and cause the first-boot postinstalls to run.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/systemd/systemd_197.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 3/26/13 11:50 AM, Ross Burton wrote:
This uses BAD_RECOMMENDATIONS which isn't supported by all package backends, but
it's a start.
Since it's not supported in all backends, can you add a bugzilla to add support
to the various backends?
--Mark
Signed-off-by: Ross Burton
We're now in the planning stages for the 1.5 release scheduled for about
6 months time. The process hasn't changed, if there are things you'd
like to see worked on in this timeframe, please ensure there are entries
for them in the bugzilla. Usually these are enhancement requests.
On Wednesday 13 March 2013 15:01:33 qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
one can use rm_work for the most of the recipes but still keep the
work area for the recipe(s) one is working on.
As an
On Tuesday 26 March 2013 12:05:33 Mark Hatle wrote:
On 3/26/13 11:50 AM, Ross Burton wrote:
This uses BAD_RECOMMENDATIONS which isn't supported by all package
backends, but it's a start.
Since it's not supported in all backends, can you add a bugzilla to add
support to the various
On 26 March 2013 17:05, Mark Hatle mark.ha...@windriver.com wrote:
On 3/26/13 11:50 AM, Ross Burton wrote:
This uses BAD_RECOMMENDATIONS which isn't supported by all package
backends, but
it's a start.
Since it's not supported in all backends, can you add a bugzilla to add
support to the
On 26 March 2013 17:12, Paul Eggleton paul.eggle...@linux.intel.com wrote:
This is a great feature, but I just looked at it and realised that the term
whitelist isn't really correct - this is more of a blacklist.
The question is does it matter? If so we should probably change it now before
it
Hi Khem,
On 21 March 2013 18:20, Khem Raj raj.k...@gmail.com wrote:
Ross, I have 198 update pactch in branch here
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/systemd-198id=51d4993c7375a7339a3ee91cf6b24da25b2d9b50
this one is good. Other two I need to address comments
On Tue, 2013-03-26 at 17:12 +, Paul Eggleton wrote:
On Wednesday 13 March 2013 15:01:33 qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
one can use rm_work for the most of the recipes but still keep
There have been some concerns raised at the TSC recently about how
transparent the Yocto Project development process is and how and where
it connects to OpenEmbedded. When you're dealing with companies and
engineers there does need to be a process with things like schedules and
in the interests of
Giuseppe
On Mar 26, 2013, at 9:17 AM, Giuseppe CONDORELLI giuseppe.condore...@st.com
wrote:
Add bash runtime dependence, required at package install time.
it would be nicer if you could find which scripts in the whole package needs
bash
separate that out into a separate package and add
On Tue, 2013-03-26 at 17:17 +0100, Giuseppe CONDORELLI wrote:
Add bash runtime dependence, required at package install time.
Where does this dependency come from?
p.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
-Original Message-
From: kerg...@gmail.com [mailto:kerg...@gmail.com] On Behalf Of Chris Larson
Sent: Monday, March 25, 2013 2:16 PM
To: Slater, Joseph
Cc: Patches and discussions about the oe-core layer
Subject: Re: [OE-core] [PATCH 1/1] dosfstools: really compile supporting
This really functions as a blacklist, not a whitelist, since we are
listing recipes to exclude. To avoid any possibility of confusion, since
this was a recent addition, rename the variable.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/classes/rm_work.bbclass | 10
On Tue, Mar 26, 2013 at 04:42:07PM +, Iorga, Cristian wrote:
Hello all,
Initial status:
QEmu machine core-image-sato.
Follow the /update/upgrade/install path as below:
Fact: bluez5, at this point, is not an upgrade path for bluez4.
Logical conclusion would be that bluez 5 and
On Tuesday 26 March 2013 17:25:52 Phil Blundell wrote:
This doesn't seem (at the risk of invoking an unintended metaphor)
entirely black or white. Maybe it should just be RM_WORK_EXCEPTIONS
or something.
exception has another meaning to my mind. I've sent out a patch to change it
to
On Tue, Mar 26, 2013 at 05:12:16PM +, Paul Eggleton wrote:
On Wednesday 13 March 2013 15:01:33 qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
one can use rm_work for the most of the recipes but still
Hi Martin,
For Case 1, I have not tested how happy were connman, ofono, and others after
the upgrade. :-) I guess they were not happy at all, at least at runtime.
Also, given your thoughts/observation, please advise on how we should proceed
on this one.
An option to postpone this upgrade until
On Tuesday 26 March 2013 18:55:14 Martin Jansa wrote:
On Tue, Mar 26, 2013 at 05:12:16PM +, Paul Eggleton wrote:
On Wednesday 13 March 2013 15:01:33 qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
On 03/26/2013 09:51 AM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
Due to recent change in the oecore layer grub-efi recipe uses separate
builddir and the paths used in the do_deply need to change accordingly.
This change avoids this build issue:
On 13-03-26 11:54 AM, Darren Hart wrote:
On 03/26/2013 08:49 AM, Bruce Ashfield wrote:
On 13-03-26 11:48 AM, Darren Hart wrote:
On 03/26/2013 07:46 AM, Bruce Ashfield wrote:
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe
debugedit from rpm has unearthed a bug in uclibc
where it was mixing stabs with elf/dwarf
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta/recipes-core/uclibc/uclibc-git.inc|5 +-
.../0001-i386-sysdep.h-Remove-STABS_-macros.patch | 71
On Tue, 2013-03-26 at 14:48 -0700, Khem Raj wrote:
debugedit from rpm has unearthed a bug in uclibc
where it was mixing stabs with elf/dwarf
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta/recipes-core/uclibc/uclibc-git.inc|5 +-
On Mar 26, 2013, at 3:52 PM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Tue, 2013-03-26 at 14:48 -0700, Khem Raj wrote:
debugedit from rpm has unearthed a bug in uclibc
where it was mixing stabs with elf/dwarf
Signed-off-by: Khem Raj raj.k...@gmail.com
---
On Tue, 2013-03-26 at 15:18 +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
This script is intended to start at runlevel 2 3 4 5, as specified
in its HEAD INFO area.
Perhaps the header is wrong?
The fact that it was not started at runlevel 3 caused splash screen
On Mar 26, 2013, at 10:18 AM, Burton, Ross ross.bur...@intel.com wrote:
Hi Khem,
On 21 March 2013 18:20, Khem Raj raj.k...@gmail.com wrote:
Ross, I have 198 update pactch in branch here
We need to get in after complementary package installation, so use
_append instead of +=.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/classes/buildhistory.bbclass |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/classes/buildhistory.bbclass
FSL gcc source is used for following gcc variants, and other gcc variants use
Yocto default source. +fsl suffix is appended into PV in below gcc recipes.
My understanding is that below gcc variants should use a different build folder
with gcc-crosssdk, am I misunderstanding something?
I might
From: Nitin A Kamble nitin.a.kam...@intel.com
This was detected on the autobuilder. More details are in the commit.
Thanks,
Nitin
The following changes since commit bdca49274173153b1b0a72887de6321b4756b684:
classes/rm_work: rename RM_WORK_WHITELIST to RM_WORK_EXCLUDE (2013-03-26
21:19:51
From: Nitin A Kamble nitin.a.kam...@intel.com
The recent change in the builddir location is breaking this recipe as
it is trying to run a script (make-image-header.sh) located in sourcedir
from builddir. As the script does not gets to run, the resulting file is
not generated causing error as seen
88 matches
Mail list logo
