On Sat, Oct 10, 2015 at 11:45:43PM +0200, Carlos Alberto Lopez Perez wrote:
> On 10/10/15 17:32, Martin Jansa wrote:
> > Did you enable thumb in that build? It's not enabled by default.
> >
> > ARM_INSTRUCTION_SET is for recipes to use arm when distro selects thumb by
> > default.
>
> I assumed i
From: Wenzong Fan
"bzip2 -t FILE" returns 2 if FILE exists, but is not a valid bzip2 file.
"bzip2 -qt FILE" returns 0 when this happens, although it does print out
an error message as is does so.
This has been fix by Debian, just port changes from Debian patch file
"20-legacy.patch":
* Fixed "b
On 10/11/2015 12:45 AM, Carlos Alberto Lopez Perez wrote:
So, could we set ARM_INSTRUCTION_SET=arm only for armv6 or older
machines in this 3 recipes?
Indeed. Webkit has other issues on armv6 or older (JIT fails to build if
you try to), so I believe the upstream developers test the builds onl
In selftest we want to exercise devtool's ability to use plugins from other
layers, so add a basic command to reverse a string to meta-selftest.
Signed-off-by: Ross Burton
---
meta-selftest/lib/devtool/__init__.py | 0
meta-selftest/lib/devtool/test.py | 15 +++
2 files changed,
Verify that devtool can use plugins in other layers by invoking the
"selftest-reverse" command provided by meta-selftest.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/selftest/devtool.py | 12
1 file changed, 12 insertions(+)
diff --git a/meta/lib/oeqa/selftest/devtool.py
b/meta/l
Hi Ross,
On Monday 12 October 2015 13:03:25 Ross Burton wrote:
> Verify that devtool can use plugins in other layers by invoking the
> "selftest-reverse" command provided by meta-selftest.
I would squash these two patches together; additionally the no-op
plugin_init() is no longer required these
On Mon, 2015-10-12 at 05:35 -0400, wenzong@windriver.com wrote:
> From: Wenzong Fan
>
> "bzip2 -t FILE" returns 2 if FILE exists, but is not a valid bzip2 file.
> "bzip2 -qt FILE" returns 0 when this happens, although it does print out
> an error message as is does so.
>
> This has been fix
The following changes since commit e42d8eff9eed7d1454b4f331d96dcee6dea232df:
bash: Disable custom memory allocator (2015-10-12 14:35:42 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/fixes4
http://cgit.openembedded.org/cgit.cgi/op
OE-Core commit 57af3fb9662106f0a65a1b4edf83e2398be0a8f1 upgraded tzdata
but also reverted a couple of changes to SUMMARY and LIC_FILES_CHKSUM.
Reinstate these (with an update to the README md5 value since that has
changed slightly, without any change to the licensing statements
within).
Signed-off
We don't need PATCHTOOL to be set to git in this recipe, and setting it
that way requires that the running user has git user & email configured,
which on a build server it might well not be.
Signed-off-by: Paul Eggleton
---
meta/recipes-devtools/build-compare/build-compare_git.bb | 1 -
1 file c
It seems that the GFDL 1.1 license file that was originally committed
was actually the 1.2 version. Replace it with the 1.1 version fetched
from http://www.gnu.org/licenses/old-licenses/fdl-1.1.txt.
Signed-off-by: Paul Eggleton
---
meta/files/common-licenses/GFDL-1.1 | 206 ++
> Am 08.10.2015 um 18:40 schrieb Khem Raj :
>
>>
>> On Oct 8, 2015, at 9:07 AM, Jens Rehsack wrote:
>>
>>
>>> Am 08.10.2015 um 16:46 schrieb Khem Raj :
>>>
>>>
On Oct 8, 2015, at 7:33 AM, Jens Rehsack wrote:
[Icedtee Ticket #2153] -- see
http://icedtea.classpath
On 11 October 2015 at 10:51, Phil Blundell wrote:
> > * gcr, libsecret are new since switch to gcc 5.2
>
> The problem with libsecret seems to be caused by its valgrind support
> code (which contains asm statements that only work in ARM state). I
> wonder if you can just turn WITH_VALGRIND off r
On Mon, Oct 12, 2015 at 9:01 AM, Jens Rehsack wrote:
>
>> Am 08.10.2015 um 18:40 schrieb Khem Raj :
>>
>>>
>>> On Oct 8, 2015, at 9:07 AM, Jens Rehsack wrote:
>>>
>>>
Am 08.10.2015 um 16:46 schrieb Khem Raj :
> On Oct 8, 2015, at 7:33 AM, Jens Rehsack wrote:
>
>
>
> Am 12.10.2015 um 18:32 schrieb Khem Raj :
>
> On Mon, Oct 12, 2015 at 9:01 AM, Jens Rehsack wrote:
>>
>>> Am 08.10.2015 um 18:40 schrieb Khem Raj :
>> [...]
>> During hacking on the fix in meta/conf/machine/ I recognized that the
>> expected thump suffix in meta/conf/machine/include/tune-arm
Under some circumstances, on OpenSUSE 13.2 qemu-native configure
can fail with the error:
ERROR: User requested feature sdl
configure was not able to find it
The following sequence can reproduce the build error:
$ bitbake libgpg-error-native
$ bitbake qemu-native
Qemu configure tests fo
Modified patch to fix
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7469
Juro Bystricky (1):
qemu: OpenSUSE 13.2 configure error
.../qemu/files/qemu-libcrypt-search-path-fix.patch | 37 ++
meta/recipes-devtools/qemu/qemu_1.7.0.bb | 2 ++
2 files changed, 39 i
On 12/10/15 13:17, Alexander Kanavin wrote:
> On 10/11/2015 12:45 AM, Carlos Alberto Lopez Perez wrote:
>
>> So, could we set ARM_INSTRUCTION_SET=arm only for armv6 or older
>> machines in this 3 recipes?
>
> Indeed. Webkit has other issues on armv6 or older (JIT fails to build if
> you try to),
On 10/12/2015 08:54 PM, Richard Purdie wrote:
On Mon, 2015-10-12 at 05:35 -0400, wenzong@windriver.com wrote:
From: Wenzong Fan
"bzip2 -t FILE" returns 2 if FILE exists, but is not a valid bzip2 file.
"bzip2 -qt FILE" returns 0 when this happens, although it does print out
an error messa
The following changes since commit e42d8eff9eed7d1454b4f331d96dcee6dea232df:
bash: Disable custom memory allocator (2015-10-12 14:35:42 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib
ChenQi/toolchain-shar-extract
http://cgit.openembedd
$env_setup_script already contains $target_sdk_dir.
Fix the path in the example.
Signed-off-by: Chen Qi
---
meta/files/toolchain-shar-extract.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/files/toolchain-shar-extract.sh
b/meta/files/toolchain-shar-extract.sh
index
21 matches
Mail list logo