On Wed, May 8, 2013 at 6:35 AM, Burton, Ross ross.bur...@intel.com wrote:
On 7 May 2013 18:57, Trevor Woerner twoer...@gmail.com wrote:
I've looked through the list of patches and don't seem to find
anything that will do what my patch needs to do in order to build
qemu-1.2.0 on openSuSE 12.3
On Wed, May 8, 2013 at 3:40 PM, Khem Raj raj.k...@gmail.com wrote:
ifconfig and its ilk (net-tools package) is deprecated in favour of iproute2
package
and is now removed by many distro's e.g. Archlinux. So we replace ifconfig
with ip utility
Signed-off-by: Khem Raj raj.k...@gmail.com
---
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 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 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 Mon, May 6, 2013 at 3:15 PM, Paul Barker p...@paulbarker.me.uk wrote:
lzip: fetch failure
This is an easy one to fix: version 1.13 is no longer available,
update the recipe (filename/hashes) to use version 1.14 instead. I
have a patch waiting to submit, but until I can register for the
On Thu, May 2, 2013 at 11:57 AM, Paul Barker p...@paulbarker.me.uk wrote:
The recipe also has dependencies
outside meta-oe (fluidsynth in meta-multimedia IIRC) but that's a
separate issue.
I've noticed that too. Shouldn't dependencies be contained within the
same layer? Is it normal from these
On Thu, May 2, 2013 at 1:22 PM, Martin Jansa martin.ja...@gmail.com wrote:
See:
http://lists.linuxtogo.org/pipermail/openembedded-devel/2013-April/045090.html
Ah yes... openembedded-devel... that magic list to which I can't seem
to subscribe myself ;-)
Would contrib/jansa/test still be the most up-to-date choice for
building against meta-openembedded?
I just want to make sure I'm not duplicating existing effort.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
All of these solutions assume the user wants to use all of their
entire computing resources to do nothing other than their Yocto build.
This isn't _always_ the case, is it? :-)
Personally, I know this build is going to take time. So I start it,
then go off and do other things with my computer. In
Sorry for not noticing this sooner.
On Thu, Apr 11, 2013 at 9:30 AM, Martin Jansa martin.ja...@gmail.com wrote:
My proposal is to add md5sum of downloaded file to ChecksumError and
rename it to file.md5sum in if isinstance(e, ChecksumError):
Would it be possible to make this behaviour
This whole thread has me thoroughly confused. Isn't xterm_277.bb already
part of meta-openembedded?
$ find . -name *xterm* -print
./meta-openembedded/meta-oe/recipes-graphics/xorg-app/xterm_277.bb
And from what I can tell, it was added over a year ago by Koen:
$ git log
On Wed, Apr 10, 2013 at 2:10 PM, Marco koansoftw...@gmail.com wrote:
Yes, it is copied from meta-openembedded into oe-core
I'm sorry, I thought the [meta-oe] in the subject line implied this
patch was destined for meta-openembedded, not coming from
meta-openembedded.
It seems rather confusing
Excellent. Now all my qemu* bitbake worlds succeed :-)
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
On Tue, Apr 9, 2013 at 10:19 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
-# We have a packages directory, add to BBFILES
+# We have recipes-* directories, add to BBFILES
[etc]
Thank you :-)
___
Openembedded-core mailing list
On Mon, Apr 8, 2013 at 1:48 PM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
Unfortunately I think this is specific to bash, so it may not be portable.
Maybe the equivalent can be achieved with sed however.
Under which shells do we expect a Yocto build to succeed? The latest
version of
On Tue, Apr 9, 2013 at 1:29 PM, Trevor Woerner twoer...@gmail.com wrote:
Under which shells do we expect a Yocto build to succeed?
Whoops! My bad.
sh - yes
bash - not so much
Let me rephrase: are bash-specific features to be so feared
On Tue, Apr 9, 2013 at 10:19 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
git://git.openembedded.org/openembedded-core-contrib paule/layer-tweaks-core
This is odd... I perform a:
$ git fetch --all
But I can only find a paule/layer-tweaks and not
paule/layer-tweaks-core. Yet the
On Tue, Apr 9, 2013 at 2:02 PM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
The openembedded-core-contrib and poky-contrib repos are entirely separate.
D'oh!
Retrying:
$ git remote add contrib git://git.openembedded.org/meta-openembedded-contrib
$ git remote -v
contrib
On Tue, Apr 9, 2013 at 2:49 PM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
Now you're looking at meta-openembedded-contrib as opposed to openembedded-
core-contrib.
So... it has come to this, eh?
http://xkcd.com/1022/
___
Openembedded-core
With a rather recent HEAD
Build Configuration:
BB_VERSION= 1.17.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = openSUSE-project-12.3
TARGET_SYS= x86_64-poky-linux
MACHINE = qemux86-64
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-20130407
On Fri, Apr 5, 2013 at 11:35 AM, maxin.j...@enea.com wrote:
+# ptest-pkgs - add -ptest packages for all ptest-enabled packages
+# (useful if you want to run the package test suites)
Is there a simple way to discover which packages are ptest-enabled?
On Fri, Apr 5, 2013 at 12:59 PM, Peter Kjellerstedt
peter.kjellerst...@axis.com wrote:
+[ ${PATH#$NEWPATHS} != $PATH ] || PATH=$NEWPATHS$PATH
This is certainly a welcome addition in functionality, but it relies
on the pattern remaining at the start of the PATH (i.e. the user
hasn't played with
I'm seeing this exact same error when I perform a bitbake world, and
have been for the last couple days
On Wed, Mar 13, 2013 at 9:43 PM, Nobuhiro Iwamatsu
nobuhiro.iwamatsu...@renesas.com wrote:
checking for i586-oe-linux-pkg-config... no
checking for pkg-config...
Is this a proposed fix for bug 3898?
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3898
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
On Fri, Mar 1, 2013 at 4:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
I'm sure about Ubuntu where it's easy:
Ubuntu-10.04 \n \
Ubuntu-11.10 \n \
Ubuntu-12.04 \n \
Ubuntu-12.10 \n \
but with others I'll need some help.
I can help with
On Fri, Mar 1, 2013 at 9:26 AM, Jason Wessel jason.wes...@windriver.com wrote:
When you using a qemuppc target and sstate you might end up with
the problem:
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index 6c44b31..eb60d43 100644
---
On Fri, Mar 1, 2013 at 11:01 AM, Martin Jansa martin.ja...@gmail.com wrote:
send lsb_release -a output
openSUSE 12.2:
$ lsb_release -a
LSB Version:
On Fri, Mar 1, 2013 at 7:00 AM, Jack Mitchell m...@communistcode.co.uk wrote:
It seems Perf is managing to have some system includes slip into the build.
Attached is the log file with details.
Strange... I can't reproduce this. I just performed a build from master adding:
Maybe we should wait until the person who reported this issue has had
the time to test this fix and confirms it works before submitting it
for inclusion?
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
On Tue, Feb 26, 2013 at 9:04 PM, Jason Wessel
jason.wes...@windriver.com wrote:
You can see the screen shots attached to the bugzilla.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3944
[ YOCTO #3944 ]
Is the Windriver logo on the VGA example optional?
On Wed, Feb 27, 2013 at 10:00 AM, tom.zanu...@linux.intel.com wrote:
From: Tom Zanussi tom.zanu...@linux.intel.com
'perf-trace' is a new perf subcommand available in the 3.8 kernel -
this patchset enables it. 'perf trace' requires libaudit, which
is added as a new recipe.
(I'm just getting
On Wed, Feb 27, 2013 at 10:00 AM, tom.zanu...@linux.intel.com wrote:
'perf-trace' is a new perf subcommand available in the 3.8 kernel -
this patchset enables it.
Out of curiosity, from where can I find the recipe(s) for a 3.8 kernel?
My meta/recipes-kernel/linux/ only includes:
On Wed, Feb 27, 2013 at 1:12 PM, Tom Zanussi
tom.zanu...@linux.intel.com wrote:
Which image are you building? I'm guessing core-image-minimal?
Yes.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
FYI
On Tue, Feb 26, 2013 at 2:52 AM, Saul Wold s...@linux.intel.com wrote:
Just curious, what's your build host arch? and what does gcc
-print-multi-os-directory return on your host?
on openSUSE 12.2
$ uname -a
Linux codei7 3.4.28-2.20-desktop #1 SMP PREEMPT Tue Jan 29 16:51:37 UTC
2013
On Tue, Feb 26, 2013 at 4:24 AM, Robert Yang liezhi.y...@windriver.com wrote:
Fix mkdebugfs.sh:
*)
echo Unknown file $FILE 12
;;
esac
I know this doesn't come from your work, but since you're making
changes, I think it would make for a better
On Tue, Feb 26, 2013 at 4:52 PM, Darren Hart dvh...@linux.intel.com wrote:
On 02/26/2013 09:53 AM, Trevor Woerner wrote:
On Tue, Feb 26, 2013 at 4:24 AM, Robert Yang liezhi.y...@windriver.com
wrote:
* Summary:
[...]now we use the mkfs.ext3/ext4 to create the image, and use
mkdebugfs.sh
On Tue, Feb 26, 2013 at 6:00 PM, Darren Hart dvh...@linux.intel.com wrote:
mkextXfs.sh ?
Likely to be confused with mke2fs itself. Perhaps:
populate-extfs.sh ?
Sounds great.
___
Openembedded-core mailing list
Just out of curiosity:
- will systemd be the default?
- will it be possible to still use/choose sysvinit (i.e. is sysvinit
going away)?
How does systemd fit in with busybox? My understanding is that busybox
has its own init system. If someone enables/chooses systemd, does it
disable busybox's
I think it would be nice (for us non-inner-circle members) if you
could link the various IRC handles to the people behind them :-)
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
(sorry I don't have the original email around to which to reply...)
For the past many years I have been accumulating various scripts which
I have used to create the root filesystems for various embedded
systems. These scripts create updates, generate artifacts for creating
bootable CF cards, and
If you are using an image in '-serial stdio' mode, temporarily change the
terminal's interrupt character to 'Ctrl-]' for the duration of the image
run. In this way, hitting 'Ctrl-C' for something running in the image
doesn't accidentally abort the entire qemu session.
Signed-off-by: Trevor
On Fri, Dec 21, 2012 at 8:00 AM, Trevor Woerner twoer...@gmail.com wrote:
+if [ x$SERIALSTDIO = x1 ]; then
+echo Escape character is '^]'
+stty intr ^]
+fi
Hold on. This should be Interrupt charater.
___
Openembedded-core mailing
If you are using an image in '-serial stdio' mode, temporarily change the
terminal's interrupt character to 'Ctrl-]' for the duration of the image
run. In this way, hitting 'Ctrl-C' for something running in the image
doesn't accidentally abort the entire qemu session.
Signed-off-by: Trevor
I'm curious to know if anyone (I certainly wouldn't be able to!) can
take a guess whether this would play nicely with external
toolchains?
In other words, if some recipe is already PROVIDES'ing
virtual/${TARGET_PREFIX}gcc etc would the correct toolchain be used
for the special packages needing
On Wed, Aug 29, 2012 at 8:49 AM, Koen Kooi k...@dominion.thruhere.net wrote:
These might not be the appropiate lists, but I might reach a few of the
culprits. Over the years people have been doing 'apt get install bitbake' or
'make install' to put bitbake into /usr/bin and after a few minutes
401 - 447 of 447 matches
Mail list logo
