Top Post:
My bad, I pushed the wrong local branch to sgw/wip, it's updated now.
Sorry.
Sau!
On 05/06/2013 08:53 PM, Randy MacLeod wrote:
On Mon, May 6, 2013 at 5:58 PM, Saul Wold s...@linux.intel.com
mailto:s...@linux.intel.com wrote:
On 05/06/2013 01:59 PM, Randy MacLeod
This way it is easier to override settings if needed.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
Hi,
this 3rd try just contains the split without the SRCREV-SRCPV mess
in earlier version. Sorry about the noise.
Cheers,
Jukka
meta/recipes-connectivity/neard/neard.inc
Hi Saul,
You are right. I will fix it.
Regards,
Cistian
-Original Message-
From: Saul Wold [mailto:s...@linux.intel.com]
Sent: Wednesday, May 01, 2013 9:21 PM
To: Iorga, Cristian
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] iptables: upgrade to 1.4.18
On
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
meta/recipes-devtools/git/{git_1.8.1.4.bb = git_1.8.2.2.bb} |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/git/{git_1.8.1.4.bb = git_1.8.2.2.bb} (65%)
diff --git
On 6 May 2013 20:47, Trevor Woerner twoer...@gmail.com wrote:
but until I can register for the
openembedded-devel mailing list I don't have anywhere to send it.
Have you tried emailing
openembedded-devel-ow...@lists.openembedded.org about the problems
you've had registering?
--
Paul Barker
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
meta/recipes-devtools/bison/{bison_2.7.bb = bison_2.7.1.bb} |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
rename meta/recipes-devtools/bison/{bison_2.7.bb = bison_2.7.1.bb} (85%)
diff --git
2013 was added in the 'Copyright' line in LICENSE.txt.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
...ons-native_2.2.0.bb = python-scons-native_2.3.0.bb} |2 +-
meta/recipes-devtools/python/python-scons_2.2.0.bb | 15 ---
The trailing slashs on Prefix=${prefix}/ and -prefix ${prefix}/ are passed
through to the generated pkgconfig files and may be joined to paths like
/include yielding a final path with a double forward-slash (eg.
/usr//include). This may end up in the debugging symbols in other applications
or
On Tue, May 07, 2013 at 12:08:02PM +0300, Bogdan Marinescu wrote:
2013 was added in the 'Copyright' line in LICENSE.txt.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
...ons-native_2.2.0.bb = python-scons-native_2.3.0.bb} |2 +-
Hi Kevin,
On 05/04/2013 12:40 AM, Kevin Strasser wrote:
Hi Laurentiu,
On Fri, May 03, 2013 at 12:01:04PM +0300, Laurentiu Palcu wrote:
do_rootfs[cleandirs] contains ${S} and, if do_rootfs task starts before
the do_dumpdata_create_diff_gz is finished, an error will occur in the
process
fix-link-failure-ip6t-NETMAP.patch removed;
already included in upstream.
Signed-off-by: Cristian Iorga cristian.io...@intel.com
---
.../iptables/fix-link-failure-ip6t-NETMAP.patch| 86
.../{iptables_1.4.17.bb = iptables_1.4.18.bb} |8 +-
2 files changed, 3
iptables/fix-link-failure-ip6t-NETMAP.patch actually removed.
-Original Message-
From: Iorga, Cristian
Sent: Tuesday, May 07, 2013 12:35 PM
To: openembedded-core@lists.openembedded.org
Cc: Iorga, Cristian
Subject: [PATCH V2] iptables: upgrade to 1.4.18
fix-link-failure-ip6t-NETMAP.patch
The max length of debugfs argument is 256 which is too short, the
arguments are two paths, the PATH_MAX is 4096 according to
/usr/include/linux/limits.h, use 2048 (4096 / 2) is a reasonable value.
[YOCTO #3848]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
* The benefits:
- Really support ext4
- Support the sparse file (the sparse file became into the common file before)
- Have a uniform code for ext2/3/4 generation
- Remove the depends on genext2fs-native
* Impact
- Build time:
a) If we build fresh core-image-sato, there is nearly no
Let debugfs do sparse copy when src is a sparse file, just like
cp --sparse=auto
[YOCTO #3848]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
.../e2fsprogs/e2fsprogs-1.42.7/sparse_copy.patch | 114
.../recipes-devtools/e2fsprogs/e2fsprogs_1.42.7.bb |1 +
2
This script is originally from Darren Hart, it will be used for creating
the ext* filesystem from a given directory, which will replace the
genext2fs in image_types.bbclass at the moment, we may use the mke2fs to
replace this script again when it has the initial directory support.
Changes of the
2013 was added in the 'Copyright' line in LICENSE.txt.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
...ons-native_2.2.0.bb = python-scons-native_2.3.0.bb} |1 -
meta/recipes-devtools/python/python-scons_2.2.0.bb | 15 ---
* The benefits:
- Really support ext4
- Support the sparse file (we lost the sparse file in the image in the
past, the sparse file became into the common file)
- Have a uniform code for ext2/3/4 generation
* Comments from Darren Hart:
Basically, genext2fs doesn't support creating ext4
On Tue, May 7, 2013 at 12:10 PM, Martin Jansa martin.ja...@gmail.comwrote:
On Tue, May 07, 2013 at 12:08:02PM +0300, Bogdan Marinescu wrote:
2013 was added in the 'Copyright' line in LICENSE.txt.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
...ons-native_2.2.0.bb =
On 5 May 2013 21:50, Carlos Rafael Giani d...@pseudoterminal.org wrote:
Installing the gstreamer -meta packages was not possible, because the
-apps and -glib packages were missing. Allowing for empty -apps/glib
packages fixes this.
From what I can tell there's only one -apps package
License changed from LGPLv2 to LGPLv3.
The automake patch was integrated upstream in a different form.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
meta/recipes-support/libmpc/libmpc.inc |2 +-
.../libmpc/libmpc_fix_for_automake-1.12.patch | 26
The following changes since commit 3472c1f7ab409cd91c1d4782d9e00880b84e3ae8:
grub-efi-native: Cleanup whitespace (2013-05-03 16:37:05 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/rm_old
Remove the obsolete image before the new one generated to save disk
space when RM_OBSOLETE_IMAGE is set to 1, this is an easy way to keep
the DEPLOY_DIR_IMAGE clean.
[YOCTO #4391]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta/classes/image_types.bbclass | 6 +-
On 05/07/2013 11:55 AM, Burton, Ross wrote:
On 5 May 2013 21:50, Carlos Rafael Giani d...@pseudoterminal.org wrote:
Installing the gstreamer -meta packages was not possible, because the
-apps and -glib packages were missing. Allowing for empty -apps/glib
packages fixes this.
From what I can
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
.../mpfr/{mpfr-3.1.1 = mpfr-3.1.2}/long-long-thumb.patch |0
meta/recipes-support/mpfr/{mpfr_3.1.1.bb = mpfr_3.1.2.bb} |8
2 files changed, 4 insertions(+), 4 deletions(-)
rename
On Tuesday 07 May 2013 18:26:59 Robert Yang wrote:
Remove the obsolete image before the new one generated to save disk
space when RM_OBSOLETE_IMAGE is set to 1, this is an easy way to keep
the DEPLOY_DIR_IMAGE clean.
[YOCTO #4391]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
On 05/07/2013 06:32 PM, Paul Eggleton wrote:
On Tuesday 07 May 2013 18:26:59 Robert Yang wrote:
Remove the obsolete image before the new one generated to save disk
space when RM_OBSOLETE_IMAGE is set to 1, this is an easy way to keep
the DEPLOY_DIR_IMAGE clean.
[YOCTO #4391]
Signed-off-by:
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
.../mpfr/{mpfr-3.1.1 = mpfr-3.1.2}/long-long-thumb.patch |0
meta/recipes-support/mpfr/{mpfr_3.1.1.bb = mpfr_3.1.2.bb} |8
2 files changed, 4 insertions(+), 4 deletions(-)
rename
On Tue, 2013-05-07 at 11:11 +0800, Olivia Yin wrote:
WARNING: QA Issue: yajl: Files/directories were installed but not shipped
/usr/lib
/usr/lib/libyajl.so.2
/usr/lib/libyajl.so
/usr/lib/libyajl_s.a
/usr/lib/libyajl.so.2.0.4
/usr/lib/.debug
/usr/lib/.debug/libyajl.so.2.0.4
On 7 May 2013 11:29, Carlos Rafael Giani d...@pseudoterminal.org wrote:
True, however I wonder if somebody relies on these packages being there.
Is it acceptable to break compatibility here?
They haven't been there for a while and 1.4 is shipping without them
so I'd endorse cleaning them up
On 05/07/2013 12:31 PM, Laurentiu Palcu wrote:
Hi Kevin,
On 05/04/2013 12:40 AM, Kevin Strasser wrote:
Hi Laurentiu,
On Fri, May 03, 2013 at 12:01:04PM +0300, Laurentiu Palcu wrote:
do_rootfs[cleandirs] contains ${S} and, if do_rootfs task starts before
the do_dumpdata_create_diff_gz is
On 05/07/2013 04:38 AM, Paul Barker wrote:
On 6 May 2013 20:47, Trevor Woerner twoer...@gmail.com wrote:
but until I can register for the
openembedded-devel mailing list I don't have anywhere to send it.
Have you tried emailing
openembedded-devel-ow...@lists.openembedded.org about the
Using before do_rootfs would have this task added to do_rootfs
dependencies regardless of the filtering options. Instead, add this
dependency in the anonymous python function.
Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com
---
meta/classes/archive-configured-source.bbclass |7
In summary its been a fairly quiet week, there are number of different
holidays in different geos.
Pending Patches
===
There has been a steady stream of 1.5 patches starting to appear. With
Saul's help these have been tested on the autobuilder and then many have
been merged into
Modern expection rasing syntax is function call format, convert to this
to keep python 3 happy and model correct coding style in the core.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/gtk-immodules-cache.bbclass |2 +-
There are some left over tab characters in the python functions. This
removes them and resolves python 3 errors.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/insane.bbclass| 26 ++--
python3 doesn't like files being left open. This updates the code style
to ensure file are closed.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/buildstats.bbclass | 31 ---
1 file changed, 16 insertions(+), 15 deletions(-)
diff
The quote characters present trigger pyhton 3 characters type warnings,
we don't need them so replace them with normal quote characters.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/recipes-core/images/core-image-minimal-initramfs.bb |2 +-
1 file changed, 1
Update older code to use modern exception handling syntax which
is the form accepted by python 3.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/base.bbclass |4 ++--
meta/classes/sanity.bbclass |6 --
meta/lib/oe/cachedpath.py |4 ++--
Currently if errors occur early in the init process, the errors may
not be shown to the user. This change ensures that if a failure does
occur, the messages are flushed from the queue and shown to the user.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
bitbake/bin/bitbake
StandardError is removed in python3, replace with Exception class instead.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/lib/oe/license.py |2 +-
meta/lib/oe/terminal.py |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
The commands module is removed in python3. Use the subprocess module instead
and the pipes module to replace the mkargs usage.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/sanity.bbclass |6 +++---
meta/lib/oe/patch.py|6 +++---
2 files
python3 is stricter about type comparisions so add an explicit cast to int()
to ensure this code is portable.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/conf/bitbake.conf |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/base.bbclass |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 196acdb..b1642a2 100644
--- a/meta/classes/base.bbclass
+++
In python 3 print is a function call. In some cases bb.note is a more
appropriate call to make.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/sanity.bbclass |7 ---
meta/classes/sstate.bbclass |6 +++---
meta/lib/oe/path.py |2 +-
3
The has_key() attribute has been removed in python 3 since there is better
syntax available. Use the improved syntax.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/image.bbclass |2 +-
meta/classes/kernel-module-split.bbclass |2 +-
We open the file we're writing to in binary mode so open the input stream with
the
same mode so things match. This avoids errors with python3.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/insane.bbclass |2 +-
1 file changed, 1 insertion(+), 1
A number of patches are now part of the upstream.
Tested by compiling and running core-image-minimal/qemux86.
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
.../gmp/gmp-5.1.0/187b7b1646ee.patch | 44
The operator is depracted, use != instead which is equavalent.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/metadata_scm.bbclass |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/metadata_scm.bbclass
file() syntax is removed in python 3, use open() instead.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/sanity.bbclass | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta/classes/sanity.bbclass
On Tue, 2013-05-07 at 13:56 +0100, Richard Purdie wrote:
The operator is depracted, use != instead which is equavalent.
typos: deprecated (both long and short messages) and equivalent
p.
___
Openembedded-core mailing list
From: Tom Zanussi tom.zanu...@linux.intel.com
This fixes QA warnings I'm seeing when building a 'traditional'
kernel recipe.
Please pull into both master and dylan.
The following changes since commit 9895d2c074156fee338d91aed7cfb0800477c622:
maintainers.inc: update sbc pkg maintainer
From: Tom Zanussi tom.zanu...@linux.intel.com
Fix QA warnings seen when using 'traditional' kernel recipes e.g.:
WARNING: QA Issue: .../recipes-kernel/linux/linux_3.0.18.bb: Variable
FILES is set as not being package specific, please fix this.
Signed-off-by: Tom Zanussi
On 2013-04-29 06:57, Phil Blundell wrote:
Nothing in this package uses xkbcomp so depending on it here is not appropriate.
Whatever package(s) is/are invoking that binary should be the ones to depend
on it.
Signed-off-by: Phil Blundell ph...@gnu.org
---
On 7 May 2013 16:13, Gary Thomas g...@mlbassoc.com wrote:
It looks like the package(s) you're referring to are the X server.
Too bad you didn't provide those patches as well as images which
use X are currently broken (at least mine are)
Yeah, I noticed that when browsing mail over breakfast
They differ at times because one is set from the db_cv_path_mkdir and the other
is
found during config time for the host (/usr/bin/mkdir), in the macros we should
just
use __mkdir for the __mkdir_p variant.
[YOCTO #4452]
Signed-off-by: Saul Wold s...@linux.intel.com
---
On Tue, May 07, 2013 at 01:55:53PM +0100, Richard Purdie wrote:
There are some left over tab characters in the python functions. This
removes them and resolves python 3 errors.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
@@ -202,13 +202,13 @@ def
On Tue, May 07, 2013 at 01:55:54PM +0100, Richard Purdie wrote:
The quote characters present trigger pyhton 3 characters type warnings,
^python^
we don't need them so replace them with normal quote characters.
Signed-off-by: Richard Purdie
On Tue, May 07, 2013 at 01:55:57PM +0100, Richard Purdie wrote:
In python 3 print is a function call. In some cases bb.note is a more
appropriate call to make.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
meta/classes/sanity.bbclass |7 ---
On 2013-05-07 09:23, Burton, Ross wrote:
On 7 May 2013 16:13, Gary Thomas g...@mlbassoc.com wrote:
It looks like the package(s) you're referring to are the X server.
Too bad you didn't provide those patches as well as images which
use X are currently broken (at least mine are)
Yeah, I noticed
OE-Core commit bdcc5e8f1286d288baf410458efc39a59b68d751 removed xkbcomp
from RDEPENDS for xkeyboard-config but X server still needs it otherwise
it fails to start.
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
---
meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 +-
1 file
On Tue, 2013-05-07 at 09:43 -0600, Gary Thomas wrote:
On 2013-05-07 09:23, Burton, Ross wrote:
On 7 May 2013 16:13, Gary Thomas g...@mlbassoc.com wrote:
It looks like the package(s) you're referring to are the X server.
Too bad you didn't provide those patches as well as images which
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all kernels and all qemu machines.
[ YOCTO #4196 ]
On 7 May 2013 16:45, Stefan Stanacar stefanx.stana...@intel.com wrote:
OE-Core commit bdcc5e8f1286d288baf410458efc39a59b68d751 removed xkbcomp
from RDEPENDS for xkeyboard-config but X server still needs it otherwise
it fails to start.
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
On 2013-05-07 09:47, Stanacar, StefanX wrote:
On Tue, 2013-05-07 at 09:43 -0600, Gary Thomas wrote:
On 2013-05-07 09:23, Burton, Ross wrote:
On 7 May 2013 16:13, Gary Thomas g...@mlbassoc.com wrote:
It looks like the package(s) you're referring to are the X server.
Too bad you didn't
On Tue, May 7, 2013 at 11:49 AM, Ross Burton ross.bur...@intel.com wrote:
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series.
Until
this can be root-caused and fixed in the kernel, disable
I'm a bit confused about what exactly meta-toolchain is building? It
seems to be bitbaking gcc and creating a toolchain with the prefix
x86_64-oesdk-linux- (default SDK_PREFIX) but I'm not sure what it is.
Is it a cross-compile for my target MACHINE or a compiler for my build
machine? Based on
On 05/07/2013 09:04 AM, Bruce Ashfield wrote:
On Tue, May 7, 2013 at 11:49 AM, Ross Burton ross.bur...@intel.com wrote:
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series.
Until
this can be
On Tue, May 7, 2013 at 8:45 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
1.3.2
=
I've merged a lot of queued changes that Ross prepared for 1.3.2 and
this is now undergoing testing.
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile
on openSuSE 12.3
On 5/7/13 11:09 AM, Kyle Farnsworth wrote:
I'm a bit confused about what exactly meta-toolchain is building? It
seems to be bitbaking gcc and creating a toolchain with the prefix
x86_64-oesdk-linux- (default SDK_PREFIX) but I'm not sure what it is.
Is it a cross-compile for my target MACHINE or
On Tue, May 7, 2013 at 12:36 PM, Mark Hatle mark.ha...@windriver.com wrote:
There are two ways to generate an SDK.
* targeted SDK -- This is a meta-toolchain* recipe that lists -exactly- what
is going to be in the SDK. This is great if you want to limit your SDK to
specific libraries for
On 5/7/13 11:49 AM, Trevor Woerner wrote:
On Tue, May 7, 2013 at 12:36 PM, Mark Hatle mark.ha...@windriver.com wrote:
There are two ways to generate an SDK.
* targeted SDK -- This is a meta-toolchain* recipe that lists -exactly- what
is going to be in the SDK. This is great if you want to
The following changes since commit 94e3f18214e2e35076c52ed27252073f788ec01f:
build-appliance: Update to latest dylan revision for release (2013-04-18
22:02:26 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/for-dylan
From: Martin Jansa martin.ja...@gmail.com
* number of TUNE_CCARGS conditionals is important if we add
extra space with each one in else branch
I'm building for 2 MACHINEs one is cortexa9, second is cortexa8
few months ago we added TUNE_CCARGS[vardepvalue] in bitbake.conf
From: Martin Jansa martin.ja...@gmail.com
Signed-off-by: Martin Jansa martin.ja...@gmail.com
Signed-off-by: Saul Wold s...@linux.intel.com
---
meta/conf/machine/include/tune-thumb.inc | 32
1 file changed, 32 deletions(-)
delete mode 100644
On 7 May 2013 17:21, Darren Hart dvh...@linux.intel.com wrote:
Have we seen the failure on 3.8? Or only on 3.4?
I've only seen it on 3.4 but it's only occasionally hitting so that
doesn't really say a huge amount. I can re-send it for 3.4 and we can
continue to watch the AB -- if it doesn't
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all kernels and all qemu machines.
[ YOCTO #4196 ]
On 13-05-07 01:08 PM, Ross Burton wrote:
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all kernels and
On 7 May 2013 17:29, Trevor Woerner twoer...@gmail.com wrote:
1.3.2
=
I've merged a lot of queued changes that Ross prepared for 1.3.2 and
this is now undergoing testing.
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile
on openSuSE 12.3 (which, apparently, is also
On 7 May 2013 18:12, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
(I also have pending updates to the latest 3.4 + LTSI, so it's worth
checking to see if they happen to help here. Or was it only when these
were applied that we started seeing this ?).
They crash is sufficiently rare that
On 05/07/2013 11:36 AM, Mark Hatle wrote:
On 5/7/13 11:09 AM, Kyle Farnsworth wrote:
I'm a bit confused about what exactly meta-toolchain is building? It
seems to be bitbaking gcc and creating a toolchain with the prefix
x86_64-oesdk-linux- (default SDK_PREFIX) but I'm not sure what it is.
On 5/7/13 12:35 PM, Kyle Farnsworth wrote:
On 05/07/2013 11:36 AM, Mark Hatle wrote:
On 5/7/13 11:09 AM, Kyle Farnsworth wrote:
I'm a bit confused about what exactly meta-toolchain is building? It
seems to be bitbaking gcc and creating a toolchain with the prefix
x86_64-oesdk-linux- (default
On Tue, May 7, 2013 at 1:13 PM, Burton, Ross ross.bur...@intel.com wrote:
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile
on openSuSE 12.3 (which, apparently, is also affected by the same (or
a similar) DSO linking change that affects fedora). Are the queued
changes
On Tue, May 7, 2013 at 1:41 PM, Mark Hatle mark.ha...@windriver.com wrote:
- nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
Is this related to the SDKMACHINE setting?
___
Openembedded-core mailing list
On 05/07/2013 10:08 AM, Ross Burton wrote:
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series.
Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all
On 5/7/13 1:21 PM, Trevor Woerner wrote:
On Tue, May 7, 2013 at 1:41 PM, Mark Hatle mark.ha...@windriver.com wrote:
- nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
Is this related to the SDKMACHINE setting?
Yes that's the variable I was thinking of. You can build an SDK
On 05/07/2013 01:35 PM, Mark Hatle wrote:
- nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
Is this related to the SDKMACHINE setting?
Yes that's the variable I was thinking of. You can build an SDK for
'i586' on your x86_64 host for instance.
So in my case, since I did
On 05/07/2013 03:34 AM, Bogdan Marinescu wrote:
Signed-off-by: Bogdan Marinescu bogdan.a.marine...@intel.com
---
.../mpfr/{mpfr-3.1.1 = mpfr-3.1.2}/long-long-thumb.patch |0
meta/recipes-support/mpfr/{mpfr_3.1.1.bb = mpfr_3.1.2.bb} |8
2 files changed, 4
On 5/7/13 2:33 PM, Kyle Farnsworth wrote:
On 05/07/2013 01:35 PM, Mark Hatle wrote:
- nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
Is this related to the SDKMACHINE setting?
Yes that's the variable I was thinking of. You can build an SDK for
'i586' on your x86_64 host
Jonathan,
This patch still does not address the issue that I mentioned in the last
email about the failing to build the native version of isohybrid.
| gcc -isystem
/srv/ssd/sgw/machines/fri2/tmp/sysroots/x86_64-linux/usr/include -O2 -o
isohybrid isohybrid.o isohdpfx.o -luuid
|
Have these been reviewed on the ext mailing list already?
--
Darren
On 05/07/2013 02:48 AM, Robert Yang wrote:
* The benefits:
- Really support ext4
- Support the sparse file (the sparse file became into the common file
before)
- Have a uniform code for ext2/3/4 generation
-
Hi Darren,
No, I haven't sent them to the ext mailing list, can we merge them in
oe-core and then back port to the ext community ? Or I should send them
to the ext mailing list first ?
// Robert
On 05/08/2013 06:48 AM, Darren Hart wrote:
Have these been reviewed on the ext mailing list
Hi Jack
since I was playing with archlinux today, I could reproduce this gcc ICE
problem with angstrom. Actual issue has been already fixed with
http://git.openembedded.org/openembedded-core/commit/?id=b1dc91969f9bb0c2a3a4336f5e9a2f57aabb9f78
but it was still failing on angstrom/cortex-a8-hf
Patches are now part of upstream or no longer needed.
Added new util-linux dependency for isohybrid.
Paths updated to reflect directory structure changes.
The sysroot isn't searched when building syslinux-native so syslinux
is unable to find the uuid header/library from util-linux when building
Some distros have newer makeinfo which does not go well with
anything below gcc 4.8, this fix avoids regenerating info files
Signed-off-by: Khem Raj raj.k...@gmail.com
---
meta/recipes-devtools/gcc/gcc-configure-cross.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git
Op 8 mei 2013, om 04:23 heeft Khem Raj raj.k...@gmail.com het volgende
geschreven:
Hi Jack
since I was playing with archlinux today, I could reproduce this gcc ICE
problem with angstrom. Actual issue has been already fixed with
96 matches
Mail list logo
