Richard,
Stemming from a thread about defconfigs not being applied, I realized that
in my final integration of aufs the patch which actually linked it into
the kernel build was dropped. As such, it hasn't been building for the
past week or so.
I've restored that patch, and built for all arches,
Updating the 3.14 SRCREVs to import the following changes:
- enable AUFS: a missing Kbuild patch was preventing aufs from compiling
- edgerouter: remove RTC configuration options
- preempt-rt recipe. The patch for 3.14 is availble, so we populate the
recipe.
Signed-off-by: Bruce Ashfield
On 04/11/2014 09:56 PM, Otavio Salvador wrote:
Hello,
On Wed, Apr 9, 2014 at 12:13 AM, Robert Yang wrote:
On 04/07/2014 10:55 PM, Valentin Popa wrote:
Indeed the build failure was introduced by that patch, which enters a
logical
conflict with the bbappend file for mesa.
To remain compatible
Running 'bitbake -e' without further arguments causes a stack trace on stderr:
| ERROR: Command execution failed: Traceback (most recent call last):
| File "[...]/bitbake/lib/bb/command.py", line 99, in runAsyncCommand
| commandmethod(self.cmds_async, self, options)
| File "[...]/bitbake/l
On 4/11/14, 10:59, "Kamble, Nitin A" wrote:
>From: Nitin A Kamble
>
>Use machine overrides for variables for this skeleton kernel recipe
>so that people following skeleton do it right at the beginning.
>
>The machine overrides for the variables reduces variable name-space
>pollution and avoids
From: Nitin A Kamble
In this v2 pull request, the commit is updated as per feedback received
from Darren.
Thanks,
Nitin
The following changes since commit 863cc7483f5ee43189537940de8ee5c0964d24cc:
poky.conf: Post release version bump (2014-04-10 18:03:07 +0100)
are available in the git repo
From: Nitin A Kamble
Use machine overrides for variables for this skeleton kernel recipe
so that people following skeleton do it right at the beginning.
The machine overrides for the variables reduces variable name-space
pollution and avoids unintentional influences on other layers.
Signed-off
On 4/11/2014 10:48 AM, Bruce Ashfield wrote:
On 14-04-11 01:05 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble
Use machine overrides for variables for this skeleton recipe so that
people following skeleton do it right at the beginning.
The machine overrides for the variables reduces
People behind a proxy couldn't send an error report to an upstream server,
this should fix the issue if they use a proxy that doesn't require
authentication,
or one that uses basic http authentication and it's correctly exported in the
enviroment.
Signed-off-by: Stefan Stanacar
---
scripts/sen
On 14-04-11 01:05 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble
Use machine overrides for variables for this skeleton recipe so that
people following skeleton do it right at the beginning.
The machine overrides for the variables reduces pollution of name space
and avoid unintentiona
On 4/11/14, 10:05, "Kamble, Nitin A" wrote:
>From: Nitin A Kamble
>
>Use machine overrides for variables for this skeleton recipe so that
>people following skeleton do it right at the beginning.
>
>The machine overrides for the variables reduces pollution of name space
>and avoid unintentional i
Actually I'll send v2 which should work for HTTP Basic Authentication
too.
On Fri, 2014-04-11 at 18:54 +0300, Stefan Stanacar wrote:
> People behind a proxy couldn't send an error report to an upstream server,
> this should fix the issue if they use a proxy that doesn't require
> authentication,
From: Nitin A Kamble
The kernel variables in kernel bbappend recipes such as LINUX_VERSION should
always use machine overrides to unintentionally influencing kernel variables
in other layers. Adding missing overrides to the kernel recipe in the
meta-skeleton layer, so people who use it to make th
From: Nitin A Kamble
Use machine overrides for variables for this skeleton recipe so that
people following skeleton do it right at the beginning.
The machine overrides for the variables reduces pollution of name space
and avoid unintentional influences on other layers.
Signed-off-by: Nitin A Ka
From: Alexandru DAMIAN
Toaster may look up inexistent file paths in the build history
for packages that have been referenced but not built.
This triggers a failure, and this patch recovers by deleting
the reference to the non-built packages.
[YOCTO #6063]
Signed-off-by: Alexandru DAMIAN
Signe
The following changes since commit 20625df0f88b1948bfc05be0d2cbdaa201c3b2f0:
linux-yocto/3.10: intel BSP configuration updates (2014-04-10 17:33:54 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/toaster-pkgdata
http://cgit.openemb
Now that we have an YP instance of the error report web interface [1],
that should be set as the default instead of localhost.
[1] http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/
Signed-off-by: Stefan Stanacar
---
scripts/send-error-report | 2 +-
1 file changed, 1 insertion(+), 1 d
People behind a proxy couldn't send an error report to an upstream server,
this should fix the issue if they use a proxy that doesn't require
authentication,
and it's correctly exported in the enviroment.
There are probbaly better ways to fix this (urllib2, proxy connect,
a command line option for
* parsing ICE_PATH="${@icc_path(bb, d)}" causes "ice" directories
to be created in every sysroot, that could be a bit confusing for
people who inherit icecc.bbclass, but disabled it
* shorten ICECC_VERSION="${@icc_version(bb, d)}" path a bit
by returning sooner when disabled
* remove ICECC_PA
Hello,
On Wed, Apr 9, 2014 at 12:13 AM, Robert Yang wrote:
> On 04/07/2014 10:55 PM, Valentin Popa wrote:
>> Indeed the build failure was introduced by that patch, which enters a
>> logical
>> conflict with the bbappend file for mesa.
>> To remain compatible with the future releases I suggest to
Op 27 mrt. 2014, om 03:29 heeft Chen Qi het volgende
geschreven:
> Replace 'rootfs' with '/dev/root' in read_only_rootfs_hook function
> to match the latest change in fstab file from the base-files recipe.
>
> The related commit is as follows.
>
> commit e8bc7a136a81a0d8df2d32dfba0920c1b28351
We don't normally do this, but with the recent CVE fixes (most
importantly the one for the serious CVE-2014-0160 vulnerability) I am
bumping PR explicitly to make it a bit more obvious that the patch has
been applied.
Signed-off-by: Paul Eggleton
---
meta/recipes-connectivity/openssl/openssl_1.0
We don't normally do this, but with the recent CVE fixes (most
importantly the one for the serious CVE-2014-0160 vulnerability) I am
bumping PR explicitly to make it a bit more obvious that the patch has
been applied.
Signed-off-by: Paul Eggleton
---
meta/recipes-connectivity/openssl/openssl_1.0
Using the free space of the host works when
oe-selftest is the only build running, but if something else
on the host remove things this will fail (as seen on AB).
Using an absurdly high value should fix this.
Signed-off-by: Stefan Stanacar
---
meta/lib/oeqa/selftest/buildoptions.py | 8 +++-
While multible hosts sharing a common sstate cache, the fist host using
bash as default shell and build apr, the second host using dash as
default shell and build apr-util, there was a failure in apr-util:
...
| /bin/sh: 0: Can't open i586-poky-linux-libtool
| make[1]: *** [dbm/apr_dbm_gdbm.lo] Err
The following changes since commit 863cc7483f5ee43189537940de8ee5c0964d24cc:
poky.conf: Post release version bump (2014-04-10 18:03:07 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-apr
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ho
26 matches
Mail list logo
