Remove older patches that have been fixed upstream, added new patch to
use the correct alias-libtool instead of ./libtool.
pkgconfig provides an internal glib library, so use it to avoid ciruclar
dependecny issues.
Signed-off-by: Saul Wold s...@linux.intel.com
---
On 05/09/2013 05:34 AM, Robert Yang wrote:
On 05/09/2013 10:23 AM, Chris Larson wrote:
On Wed, May 8, 2013 at 7:14 PM, Robert Yang
liezhi.y...@windriver.comwrote:
On 05/08/2013 08:03 PM, Mike Looijmans wrote:
On 05/08/2013 11:06 AM, Robert Yang wrote:
The bb.fatal() is defined as:
def
On 05/12/2013 10:55 PM, Paul Eggleton wrote:
On Sunday 12 May 2013 19:54:50 Phil Blundell wrote:
On Sun, 2013-05-12 at 08:40 -0700, Saul Wold wrote:
On 05/12/2013 06:27 AM, Otavio Salvador wrote:
I think so, it'd be good to have it in oe-core and allow use of vpn :)
I would like to see what
On 05/08/2013 05:41 PM, Ionut Radu wrote:
0001-doc-Fix-texinfo-table-markup-in-qemu-options.hx.patch and
3f08ffb4a4741d147634761dc053ed386243a0de.patch were backported in 1.4.1
What kind of testing did you do with qemu? Qemu even minor updates can
lead to issues since it such a core part
On Monday 13 May 2013 11:00:56 Saul Wold wrote:
On 05/12/2013 10:55 PM, Paul Eggleton wrote:
On Sunday 12 May 2013 19:54:50 Phil Blundell wrote:
On Sun, 2013-05-12 at 08:40 -0700, Saul Wold wrote:
On 05/12/2013 06:27 AM, Otavio Salvador wrote:
I think so, it'd be good to have it in
The following changes since commit f7afeeb75993b159bb8959e0309bc5eb3978a8fb:
bitbake: bitbake-layers/tinfoil: Catch up with status - recpiecache rename
(2013-05-12 18:00:46 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/cachedpath
The error is not global since we don't use from os import *, so it
should be os.error.
[YOCTO #4489]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta/lib/oe/cachedpath.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta/lib/oe/cachedpath.py
On 12/05/13 23:23, Bruce Ashfield wrote:
On 13-05-12 5:49 PM, Khem Raj wrote:
On May 12, 2013, at 10:35 AM, Saul Wold s...@linux.intel.com wrote:
On 05/12/2013 09:29 AM, Khem Raj wrote:
Hi Saul
There is one serious problem that I ran into was that qemuarm 3.8
kernel segfaulted
is it
On 05/13/2013 11:33 AM, Paul Eggleton wrote:
On Monday 13 May 2013 11:00:56 Saul Wold wrote:
On 05/12/2013 10:55 PM, Paul Eggleton wrote:
On Sunday 12 May 2013 19:54:50 Phil Blundell wrote:
On Sun, 2013-05-12 at 08:40 -0700, Saul Wold wrote:
On 05/12/2013 06:27 AM, Otavio Salvador wrote:
I
On 13 May 2013 03:58, Jonathan Liu net...@gmail.com wrote:
The connmand daemon requires libxtables.so from iptables to start up.
And the automatic dependencies-from-linkage code seems to be working just fine:
$ dpkg -I connman_1.13-r20.0.2_core2.ipk
...
Depends: iptables (= 1.4.17), dbus-1,
RP's comment:
What we're trying to do is move everything to use a standard mechanism
for reporting issues of this type (do_package). With insane.bbclass, you
can elect whether a given type of error is a warning or error and fails
the task.
* The package.bbclass had used package_qa_handle_error()
The insane has been inherited by package.bbclass and becomes a
requirement, so we can remove it from defaultsetup.conf.
Note:
You can decide whether to take this patch or not.
[YOCTO #3190]
[YOCTO #4396]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
The following changes since commit c5c1517726aa103a3cdb60abda95e28997cac7c4:
image-vmdk.bbclass: disable the NOISO = 1 (2013-05-12 09:37:21 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/qa
Refactor packaging sanity tests from package.bbclass to insane.bbclass
so that the message can respect WARN_QA (print the warning message and
go on the task) and ERROR_QA (print the error message and fail the
task).
- For the bb.warn(), give it a message name and add it to WARN_QA, then
use
My build from master this morning threw up the following:
WARNING: The recipe python-pyrex-native is trying to install files into
a shared area when those files already exist. Those files and their
manifest location are:
I did a git pull which updated connman to 1.13 and rebuilt image from
scratch clearing all temp files and work. The iptables dependency was
missing when I checked with opkg-cl on the target.
Regards,
Jonathan
On 13/05/2013, at 7:05 PM, Burton, Ross ross.bur...@intel.com wrote:
On 13 May 2013
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these patches
applied ?
My configuration:
MACHINE = qemux86
IMAGE_FSTYPES += ext4
// Robert
On 05/13/2013 12:59 PM, Jonathan Liu wrote:
Hi
Op 13 mei 2013, om 10:41 heeft Jack Mitchell m...@communistcode.co.uk het
volgende geschreven:
On 12/05/13 23:23, Bruce Ashfield wrote:
On 13-05-12 5:49 PM, Khem Raj wrote:
On May 12, 2013, at 10:35 AM, Saul Wold s...@linux.intel.com wrote:
On 05/12/2013 09:29 AM, Khem Raj wrote:
Hi
Hi Mark,
On 10/05/13 21:37, Mark Hatle wrote:
One of the key pieces of the oe-core, it must be able to work without
any additional layers. It also much be able to be tested without any
additional layers.
I personally don't have a preference for the clutter and related items
on where they
Hi Richard,
On 10/05/13 23:18, Richard Purdie wrote:
I am sure we all want a solid release so I am also sure Tomas wouldn't
put experimental version of clutter near of release.
From what I read of Tomas' emails, I actually think his plans differ
from that as he finds that aspect of OE-Core
On 05/13/2013 03:24 PM, Mike Looijmans wrote:
On 05/09/2013 05:34 AM, Robert Yang wrote:
On 05/09/2013 10:23 AM, Chris Larson wrote:
On Wed, May 8, 2013 at 7:14 PM, Robert Yang
liezhi.y...@windriver.comwrote:
On 05/08/2013 08:03 PM, Mike Looijmans wrote:
On 05/08/2013 11:06 AM, Robert
On Mon, May 13, 2013 at 05:09:18AM -0400, Robert Yang wrote:
The following changes since commit c5c1517726aa103a3cdb60abda95e28997cac7c4:
image-vmdk.bbclass: disable the NOISO = 1 (2013-05-12 09:37:21 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these
patches
applied ?
Yes, the errors occured after applying your patches.
distro conf:
On 13 May 2013 10:23, Jonathan Liu net...@gmail.com wrote:
I did a git pull which updated connman to 1.13 and rebuilt image from
scratch clearing all temp files and work. The iptables dependency was
missing when I checked with opkg-cl on the target.
I really can't replicate this - my connman
* fixes build without EXTRA_IMAGE_FEATURES defined:
ERROR: '${EXTRA_IMAGE_FEATURES}' in IMAGE_FEATURES is not a valid
image feature. Valid features: dbg-pkgs
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta/conf/bitbake.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hi Darren,
Thank you very much for your detailed review, I will fix them and send
to you and Saul again (but not to oe-core mailing list atm), then send
to ext4 mailing list, please see my comments inline.
On 05/11/2013 05:59 AM, Darren Hart wrote:
On 05/07/2013 02:48 AM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these patches
applied ?
Yes, the errors occured after
On 13 May 2013 04:58, Jonathan Liu net...@gmail.com wrote:
The /run directory needs to exist when using systemd otherwise startup
fails with the following error:
systemd[1]: Failed to mount /run: No such file or directory
This is a genuine bug, but I'm not convinced it is the whole fix.
What
On Sun, 2013-05-12 at 20:55 +0100, Paul Eggleton wrote:
That doesn't work well for software layers - it is not a good thing for
various recipes to get rebuilt just because you add meta-oe to your
configuration for example.
The protocol we've established is to add PACKAGECONFIG options to
On 13 May 2013 12:02, Phil Blundell p...@pbcl.net wrote:
That doesn't seem totally ideal either, since it means that oe-core ends
up containing a bunch of joke PACKAGECONFIG options that will break
your build if you enable them (unless you add some other layer at the
same time). Personally I
On Mon, 2013-05-13 at 12:06 +0100, Burton, Ross wrote:
The problem with bbappends is that they break every time the package
in oe-core changes version.
True, that is a nuisance. Of course, now that (in most cases) we keep
only one version of any given recipe in oe-core, there is no
On 13/05/13 12:06, Burton, Ross wrote:
The problem with bbappends is that they break every time the package
in oe-core changes version.
I see this as a good thing; if I maintain a bbappend, I want to know
when the base package changes its a version, and I get an immediate
error due to bbappend
On 13/05/2013 8:03 PM, Burton, Ross wrote:
On 13 May 2013 10:23, Jonathan Liu net...@gmail.com wrote:
I did a git pull which updated connman to 1.13 and rebuilt image from
scratch clearing all temp files and work. The iptables dependency was
missing when I checked with opkg-cl on the target.
I
On Mon, May 13, 2013 at 4:41 AM, Jack Mitchell m...@communistcode.co.uk wrote:
On 12/05/13 23:23, Bruce Ashfield wrote:
On 13-05-12 5:49 PM, Khem Raj wrote:
On May 12, 2013, at 10:35 AM, Saul Wold s...@linux.intel.com wrote:
On 05/12/2013 09:29 AM, Khem Raj wrote:
Hi Saul
There is one
Hi,
v2:
- removed the DISTRO_FEATURES as suggested by Ross,
now PACKAGECONFIG is used instead in connman.inc
- all generic vpn files are placed into connman-vpn package
and vpn plugins rdepend on it
v1:
this patchset enables OpenVPN, vpnc, L2TP and PPTP VPN
technogies in ConnMan and fixes
One needs to add following statement into local.conf or distro config
PACKAGECONFIG_append_pn-connman = openvpn vpnc l2tp pptp
in order to activate support for these VPN technogies in ConnMan.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
meta/recipes-connectivity/connman/connman.inc | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/recipes-connectivity/connman/connman.inc
b/meta/recipes-connectivity/connman/connman.inc
index 6bedfa8..25e6b22
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
meta/recipes-connectivity/connman/connman.inc | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/recipes-connectivity/connman/connman.inc
b/meta/recipes-connectivity/connman/connman.inc
index 73c7215..6bedfa8
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
meta/recipes-connectivity/connman/connman.inc | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/recipes-connectivity/connman/connman.inc
b/meta/recipes-connectivity/connman/connman.inc
index e17e0e7..638e0e2
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
meta/recipes-connectivity/connman/connman.inc | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/recipes-connectivity/connman/connman.inc
b/meta/recipes-connectivity/connman/connman.inc
index 25e6b22..e17e0e7
On 13/05/2013 8:50 PM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal
building
just now, didn't notice this error. Did the error come after these
On Mon, May 13, 2013 at 03:49:12PM +0300, Jukka Rissanen wrote:
Hi,
v2:
- removed the DISTRO_FEATURES as suggested by Ross,
now PACKAGECONFIG is used instead in connman.inc
- all generic vpn files are placed into connman-vpn package
and vpn plugins rdepend on it
v1:
this patchset
Hi Martin,
On 13.05.2013 16:39, Martin Jansa wrote:
On Mon, May 13, 2013 at 03:49:12PM +0300, Jukka Rissanen wrote:
Hi,
v2:
- removed the DISTRO_FEATURES as suggested by Ross,
now PACKAGECONFIG is used instead in connman.inc
- all generic vpn files are placed into connman-vpn package
On Mon, 2013-05-13 at 16:55 +0300, Jukka Rissanen wrote:
On 13.05.2013 16:39, Martin Jansa wrote:
Jukka Rissanen (5):
connman: Add VPN support
connman: Add OpenVPN support
connman: Add vpnc support
connman: Add L2TP support
connman: Add PPTP support
I think that 2-5
On 13 May 2013 12:29, Jonathan Liu net...@gmail.com wrote:
The connmand daemon was complaining about libxtables.so.9 missing, but it's
libxtables.so.10 now.
Maybe I just had to force a more complete rebuild.
iptables upgrading should have caused connman to rebuild against the
new iptables and
On 13 May 2013 12:32, Tomas Frydrych tf+lists.yo...@r-finger.com wrote:
On 13/05/13 12:06, Burton, Ross wrote:
The problem with bbappends is that they break every time the package
in oe-core changes version.
I see this as a good thing; if I maintain a bbappend, I want to know
when the base
On Mon, May 13, 2013 at 03:04:11PM +0100, Phil Blundell wrote:
On Mon, 2013-05-13 at 16:55 +0300, Jukka Rissanen wrote:
On 13.05.2013 16:39, Martin Jansa wrote:
Jukka Rissanen (5):
connman: Add VPN support
connman: Add OpenVPN support
connman: Add vpnc support
On Mon, 2013-05-13 at 12:32 +0100, Tomas Frydrych wrote:
On 13/05/13 12:06, Burton, Ross wrote:
The problem with bbappends is that they break every time the package
in oe-core changes version.
I see this as a good thing; if I maintain a bbappend, I want to know
when the base package
On 27 April 2013 02:57, Robert Yang liezhi.y...@windriver.com wrote:
Thanks for the review, please see more comments:
The glib-2.0-native had already depend on python-native before this patch,
the depends chain is:
glib-2.0-native - python-argparse-native - python-native
That argparse usage
On Mon, 2013-05-13 at 15:49 +0300, Jukka Rissanen wrote:
+do_install_append_${PN}-vpn() {
+ mkdir -p ${D}${libdir}/connman/scripts
+ mkdir -p ${D}${libdir}/connman/plugins-vpn
+}
+
Does that actually do anything useful?
+bb.note( Adding rdependency on %s to %s % ( rdepends, package
On Mon, May 13, 2013 at 12:18 PM, Burton, Ross ross.bur...@intel.com wrote:
On 27 April 2013 02:57, Robert Yang liezhi.y...@windriver.com wrote:
Thanks for the review, please see more comments:
The glib-2.0-native had already depend on python-native before this patch,
the depends chain is:
On 13 May 2013 16:23, Otavio Salvador ota...@ossystems.com.br wrote:
We may need to have a mechanism to specific build dependencies for
native depending on host version/distribution.
The situation is that Suse splits the expat parser into a separate
package for some reason, so the fix is to
Since 2.20 the use of argparse was removed, so we don't need these dependencies
anymore.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-core/glib-2.0/glib-2.0_2.36.0.bb |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On Mon, May 13, 2013 at 12:28 PM, Burton, Ross ross.bur...@intel.com wrote:
On 13 May 2013 16:23, Otavio Salvador ota...@ossystems.com.br wrote:
We may need to have a mechanism to specific build dependencies for
native depending on host version/distribution.
The situation is that Suse splits
On Mon, 2013-05-13 at 10:30 +0100, Tomas Frydrych wrote:
Yes, but the clutter packages are not being tested, and more to the
point, they cannot be meaningfully tested using oe-core, because such
testing has to be done against a real OGL/GLES implementation -- Clutter
can only be tested
On 13 May 2013 16:41, Phil Blundell p...@pbcl.net wrote:
It seems a bit hyperbolic to claim that testing clutter is impossible
without GPU hardware (either real or emulated). The majority of the
code even in cogl, and virtually all the code in clutter itself, is
mostly independent of the
the
resulting image properly.
Build Configuration:
BB_VERSION= 1.19.0
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = openSUSE-project-12.3
TARGET_SYS= mips64-poky-linux
MACHINE = qemumips64
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-20130513
TUNE_FEATURES
On 05/13/2013 05:23 PM, Radu, IonutX wrote:
From: Saul Wold [s...@linux.intel.com]
Sent: Monday, May 13, 2013 11:20 AM
To: Radu, IonutX
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 6/9] qemu: Updated from 1.4.0 to 1.4.1
On
Changelog since 2013-05-05 until 2013-05-12. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
TARGET_SYS= mips64-poky-linux
MACHINE = qemumips64
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-20130513
TUNE_FEATURES = n64 bigendian fpu-hard
TARGET_FPU=
meta
meta-yocto
meta-yocto-bsp
On Mon, May 13, 2013 at 2:33 PM, Khem Raj raj.k...@gmail.com wrote:
On May 13, 2013, at 9:45 AM, Trevor Woerner twoer...@gmail.com wrote:
try runqemu qemumips64 bootparams=root=/dev/sda
does that boot ?
It gets a little further but doesn't succeed. I have now tried booting a
number of
times
On May 13, 2013, at 11:53 AM, Trevor Woerner twoer...@gmail.com wrote:
Process swapper (pid: 1, threadinfo=980007c8, task=980007c38000,
tls=)
Stack : 980007c83ce0 980007c83ce0 008b 809b
980007c83d00 0006
On Mon, May 13, 2013 at 2:53 PM, Trevor Woerner twoer...@gmail.com wrote:
On Mon, May 13, 2013 at 2:33 PM, Khem Raj raj.k...@gmail.com wrote:
On May 13, 2013, at 9:45 AM, Trevor Woerner twoer...@gmail.com wrote:
try runqemu qemumips64 bootparams=root=/dev/sda
does that boot ?
It gets a
On Mon, May 13, 2013 at 3:02 PM, Khem Raj raj.k...@gmail.com wrote:
you must be using systemd. I am seeing same failure with systemd but only
when my build host is archlinux
Are you referring to the build host or target? My build host is
openSuSE 12.3 which does use systemd. For the target I'm
There's something else that's going on that is strange. When I do a
qemumips build from the master repositories and run it, the
qemu-system-mips that is used is the one built as part of OE (i.e. the
one from the build sysroot). But when I build and run the qemumips64
image using this branch, the
On Mon, 13 May 2013, Trevor Woerner wrote:
There's something else that's going on that is strange. When I do a
qemumips build from the master repositories and run it, the
qemu-system-mips that is used is the one built as part of OE (i.e.
the one from the build sysroot). But when I build and
On Mon, May 13, 2013 at 3:38 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
having unwisely wandered into this MIPS64 minefield a couple weeks
back, i might as well see if i can get a build. in short:
* switch to kraj/qemumips64 branch of openembedded-core-contrib
* add that as another
On Mon, 13 May 2013, Trevor Woerner wrote:
On Mon, May 13, 2013 at 3:38 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
having unwisely wandered into this MIPS64 minefield a couple weeks
back, i might as well see if i can get a build. in short:
* switch to kraj/qemumips64 branch
On Mon, 13 May 2013, Trevor Woerner wrote:
On Mon, May 13, 2013 at 3:38 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
having unwisely wandered into this MIPS64 minefield a couple weeks
back, i might as well see if i can get a build. in short:
* switch to kraj/qemumips64 branch
On Mon, May 13, 2013 at 3:59 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Mon, 13 May 2013, Trevor Woerner wrote:
On Mon, May 13, 2013 at 3:38 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
having unwisely wandered into this MIPS64 minefield a couple weeks
back, i might as
On Mon, 13 May 2013, Bruce Ashfield wrote:
On Mon, May 13, 2013 at 3:59 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
so, once the build finishes, should i be expecting to run anything
other than (if memory serves):
$ runqemu qemumips64
??? any known issues or surprises?
On Mon, 13 May 2013, Bruce Ashfield wrote:
That's all you need, here's my output:
root@qemumips64:~# uname -a
Linux qemumips64 3.8.11-yocto-standard #1 PREEMPT Mon May 13 15:47:58
EDT 2013 mips64 GNU/Linux
That's built from scratch on Yocto master. So clearly there's
something strange
DISTRO_VERSION= 1.3+snapshot-20130513
TUNE_FEATURES = m32 core2
TARGET_FPU=
meta-yocto= master:94d31b0b36be389710bfb1c5d7aeacda92efad5b
meta-minnow = master:d474c4304dc1c9e9703fce0cd6a4329289681f92
meta-intel= master:624aada76d2de84bd0263065b112ed4e94798b6b
meta
On Mon, May 13, 2013 at 4:51 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Mon, 13 May 2013, Bruce Ashfield wrote:
That's all you need, here's my output:
root@qemumips64:~# uname -a
Linux qemumips64 3.8.11-yocto-standard #1 PREEMPT Mon May 13 15:47:58
EDT 2013 mips64 GNU/Linux
On Mon, 13 May 2013, Bruce Ashfield wrote:
On Mon, May 13, 2013 at 4:51 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On Mon, 13 May 2013, Bruce Ashfield wrote:
That's all you need, here's my output:
root@qemumips64:~# uname -a
Linux qemumips64 3.8.11-yocto-standard #1 PREEMPT
On Mon, 13 May 2013, Bruce Ashfield wrote:
On Mon, May 13, 2013 at 4:51 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On Mon, 13 May 2013, Bruce Ashfield wrote:
That's all you need, here's my output:
root@qemumips64:~# uname -a
Linux qemumips64 3.8.11-yocto-standard #1 PREEMPT
Bruce, you said you were building 3.8.11, but I'm not. When I run my image,
my banner includes:
Linux version 3.4.43-yocto-standard (trevor@zzz) (gcc version 4.7.2 (GCC) )
#1 PREEMPT Mon May 13 12:14:42 EDT 2013
___
Openembedded-core mailing list
On Mon, 13 May 2013, Trevor Woerner wrote:
Bruce, you said you were building 3.8.11, but I'm not. When I run my image,
my banner includes:
Linux version 3.4.43-yocto-standard (trevor@zzz) (gcc version 4.7.2 (GCC) )
#1 PREEMPT Mon May 13 12:14:42 EDT 2013
from my build:
$ bitbake -s |
I'm building core-image-minimal, I assume that's what everyone else is
doing.
When I run the bitbake -s as Robert is, I get the following:
$ bitbake -s | grep linux
linux-dummy :1.0-r1
linux-firmware
On Mon, 13 May 2013, Trevor Woerner wrote:
I'm building core-image-minimal, I assume that's what everyone else is doing.
When I run the bitbake -s as Robert is, I get the following:
$ bitbake -s | grep linux
linux-dummy :1.0-r1
-linux
MACHINE = minnow
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-20130513
TUNE_FEATURES = m32 core2
TARGET_FPU=
meta-yocto= master:94d31b0b36be389710bfb1c5d7aeacda92efad5b
meta-minnow = master:d474c4304dc1c9e9703fce0cd6a4329289681f92
meta
On Mon, May 13, 2013 at 5:30 PM, Robert P. J. Day rpj...@crashcourse.cawrote:
On Mon, 13 May 2013, Trevor Woerner wrote:
I'm building core-image-minimal, I assume that's what everyone else is
doing.
When I run the bitbake -s as Robert is, I get the following:
$ bitbake -s | grep linux
On Mon, 13 May 2013, Trevor Woerner wrote:
On Mon, May 13, 2013 at 5:30 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On Mon, 13 May 2013, Trevor Woerner wrote:
I'm building core-image-minimal, I assume that's what everyone else is
doing.
When I run the bitbake -s as Robert
On Mon, 13 May 2013, Bruce Ashfield wrote:
On Mon, May 13, 2013 at 4:51 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On Mon, 13 May 2013, Bruce Ashfield wrote:
That's all you need, here's my output:
root@qemumips64:~# uname -a
Linux qemumips64 3.8.11-yocto-standard #1 PREEMPT
Robert and Trevor
so whats your cross-gcc version ?
should be in tmpdir under
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc -v
On May 13, 2013, at 3:07 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Mon, 13 May 2013, Bruce Ashfield wrote:
On Mon, May
Okay, I'm going to start over :-)
I have a layer, meta-poky, which is:
$ git remote -v
contrib git://git.pokylinux.org/poky-contrib (fetch)
contrib git://git.pokylinux.org/poky-contrib (push)
origin git://git.yoctoproject.org/poky (fetch)
origin git://git.yoctoproject.org/poky (push)
Currently
On Mon, May 13, 2013 at 5:30 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
i'm confused ... why would you be building two versions of the
kernel?
Maybe I just need to provide a PREFERRED_PROVIDER_virtual/kernel?
___
Openembedded-core mailing
On Mon, 13 May 2013, Khem Raj wrote:
Robert and Trevor
so whats your cross-gcc version ?
should be in tmpdir under
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc
-v
in the middle of a fresh build just to play it safe, i should know
in a few minutes. so
On Mon, May 13, 2013 at 6:19 PM, Khem Raj raj.k...@gmail.com wrote:
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc
-v
angstrom??!
angstrom - poky?
sysroots/x86_64-linux/usr/bin/mips64-poky-linux/mips64-poky-linux-gcc --version
mips64-poky-linux-gcc (GCC) 4.7.2
On Mon, 13 May 2013, Khem Raj wrote:
Robert and Trevor
so whats your cross-gcc version ?
should be in tmpdir under
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc
-v
my build is still going but i don't have a mips64-angstrom-linux
directory, i have a
On May 13, 2013, at 3:50 PM, Trevor Woerner twoer...@gmail.com wrote:
On Mon, May 13, 2013 at 6:19 PM, Khem Raj raj.k...@gmail.com wrote:
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc
-v
angstrom??!
angstrom - poky?
doesn't matter whatever your distro
On Mon, 13 May 2013, Khem Raj wrote:
Robert and Trevor
so whats your cross-gcc version ?
should be in tmpdir under
sysroots/x86_64-linux/usr/bin/mips64-angstrom-linux/mips64-angstrom-linux-gcc
-v
after a fresh build, each attempt to boot qemumips64 hangs at some
point. i am definitely
OK, got it, I will file a new patch sooner.
// Robert
On 05/13/2013 11:28 PM, Burton, Ross wrote:
On 13 May 2013 16:23, Otavio Salvador ota...@ossystems.com.br wrote:
We may need to have a mechanism to specific build dependencies for
native depending on host version/distribution.
The
By adding:
PREFERRED_VERSION_linux-yocto := 3.8%
to my conf/local.conf I was able to get the image to build/use 3.8.11;
but I too am still seeing the kernel panic as described before (i.e.
in reset_counters()).
___
Openembedded-core mailing list
cool, keep tuned I might have narrowed it down
On May 13, 2013, at 7:01 PM, Trevor Woerner twoer...@gmail.com wrote:
By adding:
PREFERRED_VERSION_linux-yocto := 3.8%
to my conf/local.conf I was able to get the image to build/use 3.8.11;
but I too am still seeing the kernel panic as
On Mon, May 13, 2013 at 10:01 PM, Trevor Woerner twoer...@gmail.com wrote:
By adding:
PREFERRED_VERSION_linux-yocto := 3.8%
Yep. This is what I was about to recommend, but did you apply Khem's patches, or
use his contrib branch ? The 3.4 kernel has no compatibility with
qemumips64, so it
On Mon, May 13, 2013 at 10:03 PM, Bruce Ashfield
bruce.ashfi...@gmail.com wrote:
On Mon, May 13, 2013 at 10:01 PM, Trevor Woerner twoer...@gmail.com wrote:
By adding:
PREFERRED_VERSION_linux-yocto := 3.8%
Yep. This is what I was about to recommend, but did you apply Khem's patches,
or
On Mon, May 13, 2013 at 10:18 PM, Trevor Woerner twoer...@gmail.com wrote:
On Mon, May 13, 2013 at 10:03 PM, Bruce Ashfield
bruce.ashfi...@gmail.com wrote:
On Mon, May 13, 2013 at 10:01 PM, Trevor Woerner twoer...@gmail.com wrote:
By adding:
PREFERRED_VERSION_linux-yocto := 3.8%
Yep.
can you try this
add
SRCREV_machine_qemumips64 = bbefde394205a1b317eae31942bfc13afce0b0ac
to linux-yocto_3.8.bb
and rebuild the kernel and see if that boots
On May 13, 2013, at 7:18 PM, Trevor Woerner twoer...@gmail.com wrote:
On Mon, May 13, 2013 at 10:03 PM, Bruce Ashfield
On 05/14/2013 06:36 AM, Slater, Joseph wrote:
-Original Message-
From: Saul Wold [mailto:s...@linux.intel.com]
Sent: Friday, May 10, 2013 3:00 PM
To: Burton, Ross; Slater, Joseph
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] sysvinit: modify bootlog
1 - 100 of 101 matches
Mail list logo
