On Sat, Mar 11, 2017 at 1:02 PM, Martin Jansa wrote:
> This time the results are very inconsistent across different MACHINEs
> because they were using significantly different metadata.
>
> qemuarm is oldest 3 from 4 failures were causes by pending meta-oe
> changes which I've removed from master-n
On Sun, Mar 12, 2017 at 12:29 AM, Mark Asselstine
wrote:
> On Sat, Mar 11, 2017 at 1:02 PM, Martin Jansa wrote:
>> This time the results are very inconsistent across different MACHINEs
>> because they were using significantly different metadata.
>>
>> qemuarm is oldest 3 from 4 failures were caus
On 3/11/17 1:30 PM, Khem Raj wrote:
> The following changes since commit a47e64d985a610535449730806651f5bfd75d9ec:
>
> libcomps: add a recipe (2017-03-11 16:08:50 +)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib kraj/pu
> http://
Configure has an unbridled check for llvm and
when distro provided llvm is installed on build host it
will use that from /usr/bin to poke for llvm libs
and configs. This would result in a subtle errors
however do_qa_configure catches it as a host include/lib
contamination during configure checks
E
The following changes since commit a47e64d985a610535449730806651f5bfd75d9ec:
libcomps: add a recipe (2017-03-11 16:08:50 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/pu
http://cgit.openembedded.org/openembedded-core-contrib/log/?h
This time the results are very inconsistent across different MACHINEs
because they were using significantly different metadata.
qemuarm is oldest 3 from 4 failures were causes by pending meta-oe
changes which I've removed from master-next before qemux86* builds were
restarted (after they failed ba
As of ccache-3.3, ccache will always include the current directory
in the hash when the compiler is configured to output debug
information. The current directory will change every time ${PV}
changes, which will invalidate the cache.
ccache apparently does this so that paths in the debug informatio
On Sat, 2017-03-11 at 11:22 +, Richard Purdie wrote:
> On Fri, 2017-03-10 at 13:24 +0200, Alexander Kanavin wrote:
> > diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb
> > b/meta/recipes-core/base-files/base-files_3.0.14.bb
> > index d1380053115..c7a9e803cb1 100644
> > --- a/meta/
On Sat, 2017-03-11 at 13:47 +, Richard Purdie wrote:
> On Thu, 2017-03-09 at 22:23 +0200, Alexander Kanavin wrote:
> >
> > Signed-off-by: Alexander Kanavin > >
> > ---
> > ...-Avoid-host-contamination-from-gpg-config.patch | 28
> > ++
> > .../0001-Correctly-install-pytho
Otherwise cc may be used which isn't correct.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/yasm/yasm_1.3.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/yasm/yasm_1.3.0.bb
b/meta/recipes-devtools/yasm/yasm_1.3.0.bb
index 78702ed..31af1e2 100644
--- a/
OE needs to be able to change the default compiler. If we pass in HOSTCC
through the make command, it overwrites not only this setting but also the
setting in tools/Makefile wrapped in ifneq ($(CROSS_BUILD_TOOLS),) which
breaks the build.
We therefore add a way of changing the default in the top l
From: Jack Mitchell
There was a race condition in the uboot-extlinux bbclass where
only a half written extlinux.conf would be put in the deploy
directory. Fix this by adding the deploy task after the do_install
rather than after the do_compile.
Signed-off-by: Jack Mitchell
---
meta/recipes-bsp
From: Jack Mitchell
Also fixes a use before defined bug with localdata.
Signed-off-by: Jack Mitchell
---
meta/classes/uboot-extlinux-config.bbclass | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/meta/classes/uboot-extlinux-config.bbclass
b/meta/classes/ub
On Thu, 2017-03-09 at 22:23 +0200, Alexander Kanavin wrote:
> Signed-off-by: Alexander Kanavin
> ---
> ...-Avoid-host-contamination-from-gpg-config.patch | 28
> ++
> .../0001-Correctly-install-python-modules.patch| 26
>
> meta/recipes-support/gpgme/g
On Fri, 2017-03-10 at 13:24 +0200, Alexander Kanavin wrote:
> This is causing a problem in multilib where base-files and lib64/32-
> base-files
> clash because they may have different dates. Also, if the package is
> coming
> from sstate it has an incorrect date anyway.
>
> Signed-off-by: Alexande
On Sat, 2017-03-11 at 06:14 +0100, Peter Kjellerstedt wrote:
> I have been trying out the whitelisting of tools in $PATH, and it
> seems to work very well. However, one thing that I realized is that
> the tools used by the various fetchers need to be whitelisted. This
> patch adds sftp to HOSTTOOLS
On Sat, 11 Mar 2017, Khem Raj wrote:
> On 3/11/17 12:30 AM, Robert P. J. Day wrote:
> >
> > potentially a dumb question, but do the settings in
> > files/fs-perms.txt affect the building of the base-files rpm just
> > as they would affect the building of any other rpm?
>
> it should be executing
On 3/11/17 12:30 AM, Robert P. J. Day wrote:
>
> potentially a dumb question, but do the settings in
> files/fs-perms.txt affect the building of the base-files rpm just as
> they would affect the building of any other rpm?
it should be executing fixup_perms() in PKGD before splitting the
pack
* Remove duplicate entry for /srv already defined earlier in file.
* Use "${localstatedir}" rather than "/var" for consistency.
Signed-off-by: Robert P. J. Day
---
i'm assuming neither of these changes would cause any trouble.
diff --git a/meta/files/fs-perms.txt b/meta/files/fs-perms.txt
i
potentially a dumb question, but do the settings in
files/fs-perms.txt affect the building of the base-files rpm just as
they would affect the building of any other rpm?
i can see the structure of the base-files recipe, whose do_install()
routine manually installs a ton of stuff, with very sp
20 matches
Mail list logo
