From: Denys Dmytriyenko
busybox' default configuration enables dc app, which bc also provides,
setup update-alternatives to resolve the conflict.
Signed-off-by: Denys Dmytriyenko
---
meta/recipes-extended/bc/bc_1.06.bb | 13 +++--
1 files changed, 11 insertions(+), 2 deletions(-)
di
I IMAGE_INSTALL_append or IMAGE_INSTALL_append_pn-core-image-minimal or
whatever when I need to quickly add a package temporarily, myself.
--
Christopher Larson
On Tuesday, March 27, 2012 at 7:42 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 27, 2012 at 08:27:02PM +0100, Paul Eggleton wrote:
> >
On Tue, Mar 27, 2012 at 08:27:02PM +0100, Paul Eggleton wrote:
> On Tuesday 27 March 2012 08:20:11 Robert P. J. Day wrote:
> > i'm currently poring over the OE docs (including the ones at the
> > yocto site), and i'm trying to figure out how to simply add a package
> > to an image through one's l
More details in patch header
Signed-off-by: Khem Raj
---
.../recipes-extended/zypper/zypper/gcc-scope.patch | 20
meta/recipes-extended/zypper/zypper_git.bb |3 ++-
2 files changed, 22 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-extended/zypp
There are a few extra task that modify the source tree that should
be removed when externalsrc is inherited by a recipe that uses a
linux-yocto tree.
Adding those tasks to SRCTREECOVEREDTASKS means that they are skipped
and externalsrc works as intended.
Signed-off-by: Bruce Ashfield
---
meta/c
Richard/Saul,
This is a fix for externalsrc builds when the linux-yocto bbclass
is used.
The commit tells most of the story:
-
There are a few extra task that modify the source tree that should
be removed when externalsrc is inherited by a recipe that uses a
linux-yocto tree.
Adding those
armv7 is least common denominator of armv7-a
armv7-m and armv7-r and armv7-m does not support
ARM instructions but only thumb2 instruction set
which means armv7 when chosen will complain if
code is compiled in arm mode which is default
in OE if not specified other wise
if we chose this tuning erro
armv7 is least common denominator of armv7-a
armv7-m and armv7-r and armv7-m does not support
ARM instructions but only thumb2 instruction set
which means armv7 when chosen will complain if
code is compiled in arm mode which is default
in OE if not specified other wise
if we chose this tuning erro
On Wed, 28 Mar 2012, Richard Purdie wrote:
> Well, there are:
>
> bitbake -g (and look at task-depends.dot)
> bitbake -g -u depexp
> bitbake core-image-sato -n (dry run)
>
> which will give some interesting info.
yup, i'd already run across those and made a note of them.
> > p.s. one thing i'
On Tue, 2012-03-27 at 17:48 -0400, Robert P. J. Day wrote:
> so, let's say i've decided to use oe-core to build a qemux86 image:
>
> $ . oe-core/oe-init-build-env builds/qemux86
>
> before i go *any* further (before i even decide which image i'm going
> to bake), how much can bitbake tell me abou
On Mon, Mar 26, 2012 at 7:24 PM, Xiaofeng Yan wrote:
> From: Xiaofeng Yan
>
> 1 Archive sources in ${S} in the different stage
> (do_unpack,do_patch,do_configure).
> 2 Archive patches including series
> 3 Archive logs including scripts (.bb and .inc files)
> 4 dump environment resources which sh
On Tue, Mar 27, 2012 at 3:13 PM, Mark Hatle wrote:
> On 3/27/12 4:57 PM, Christopher Larson wrote:
>>
>> On Tuesday, March 27, 2012 at 2:50 PM, Mark Hatle wrote:
>>>
>>> On 3/27/12 4:05 PM, Chris Larson wrote:
>>>
>>> On PowerPC TUNE_PKGARCH should be set to powerpc (or overriden by the
>>> machin
only recently did i run across what appears to be the proper way to
define a local premirror where i've collected source tarballs over the
years, by adding the following to my local.conf:
SOURCE_MIRROR_URL ?= "file:///home/rpjday/dl/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
#
On 3/27/12 4:57 PM, Christopher Larson wrote:
On Tuesday, March 27, 2012 at 2:50 PM, Mark Hatle wrote:
On 3/27/12 4:05 PM, Chris Larson wrote:
On PowerPC TUNE_PKGARCH should be set to powerpc (or overriden by the machines).
On PowerPC64, it should be set to powerpc64. If this is not happening t
On Fri, Mar 23, 2012 at 1:00 AM, Samuel Stirtzel
wrote:
> There is a layer called meta-multimedia, would giflib, libpng and the
> others fit into it?
>From what you explained in another thread on its usage in KDE I think
its better to have a copy of it in meta-kde FWIW since if KDE switched
to us
On Tuesday, March 27, 2012 at 2:50 PM, Mark Hatle wrote:
> On 3/27/12 4:05 PM, Chris Larson wrote:
>
>
>
>
> On PowerPC TUNE_PKGARCH should be set to powerpc (or overriden by the
> machines).
> On PowerPC64, it should be set to powerpc64. If this is not happening that is
> the bug, lack of the
On Tue, 27 Mar 2012, Paul Eggleton wrote:
> On Tuesday 27 March 2012 17:33:18 Robert P. J. Day wrote:
> > the only thing a beginner might want to do is check that the dev host
> > has all essential S/W for OE work. i know that's documented in the
> > yocto QS guide here:
> >
> > http://www.yoctop
From: Peter Seebach
The various local patches have made it into upstream, so we update
the build files and jump to pseudo 1.3. This also includes a popen()
fix which fixes some edge cases that caused failures trying to check
git branches and the like.
[Yocto bug #2181]
Signed-off-by: Seebs
U
Attempt to detect when pseudo-native has been updated. If it has been updated,
or if the user is attempting an operation with pseudo-native in the name, force
a build of pseudo-native, prior to running the main build.
Note: This causes a build, then clean in the case of
bitbake -c cleansstate
Update pseudo to version 1.3 in order to fix Yocto Project bug #2181.
>From the pseudo author:
This patch updates pseudo to 1.3. The biggest change is the creation of
a new popen() wrapper, which fixes some strange PSEUDO_PREFIX errors that
could occur running certain commands (those using os.po
On 3/27/12 4:05 PM, Chris Larson wrote:
On Tue, Mar 27, 2012 at 1:22 PM, Mark Hatle wrote:
Patch 1 and 2 look fine, but I have questions on this one
On 3/27/12 2:51 PM, Christopher Larson wrote:
From: Christopher Larson
This allows setting DEFAULTTUNE to powerpc or powerpc-nf rather th
so, let's say i've decided to use oe-core to build a qemux86 image:
$ . oe-core/oe-init-build-env builds/qemux86
before i go *any* further (before i even decide which image i'm going
to bake), how much can bitbake tell me about this configuration?
i know
$ bitbake -e
can tell me my curren
On Tuesday 27 March 2012 17:33:18 Robert P. J. Day wrote:
> the only thing a beginner might want to do is check that the dev host
> has all essential S/W for OE work. i know that's documented in the
> yocto QS guide here:
>
> http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project
On Tue, Mar 27, 2012 at 2:33 PM, Robert P. J. Day wrote:
> $ git clone git://git.openembedded.org/openembedded-core oe-core
> $ cd oe-core
> $ git clone git://git.openembedded.org/bitbake bitbake
>
> the only thing a beginner might want to do is check that the dev host
> has all essential S/W for
assuming all i've done so far is:
$ git clone git://git.openembedded.org/openembedded-core oe-core
$ cd oe-core
$ git clone git://git.openembedded.org/bitbake bitbake
the only thing a beginner might want to do is check that the dev host
has all essential S/W for OE work. i know that's documen
* All procps tools print a message like this when the kernel
version consists of only two numbers:
| Non-standard uts for running kernel:
| release ... gives version code ...
* Import a patch from Debian to quieten this message.
Signed-off-by: Andreas Oberritter
---
.../procps/procps-3.2.8/g
On Mon, Mar 26, 2012 at 7:24 PM, Xiaofeng Yan
wrote:
> From: Xiaofeng Yan
>
> 1 Archive sources in ${S} in the different stage
> (do_unpack,do_patch,do_configure).
> 2 Archive patches including series
> 3 Archive logs including scripts (.bb and .inc files)
> 4 dump environment resources which sh
On Tue, Mar 27, 2012 at 2:00 PM, Robert P. J. Day wrote:
> the setup: for better or worse, i and a local colleague are
> submitting a proposal to give a 1/2-day tutorial on OE/yocto at this
> year's ottawa linux symposium:
>
> http://www.linuxsymposium.org/2012/
>
> and my plan is to start from
On Tue, Mar 27, 2012 at 1:22 PM, Mark Hatle wrote:
> Patch 1 and 2 look fine, but I have questions on this one
>
>
> On 3/27/12 2:51 PM, Christopher Larson wrote:
>>
>> From: Christopher Larson
>>
>> This allows setting DEFAULTTUNE to powerpc or powerpc-nf rather than just
>> the
>> more speci
the setup: for better or worse, i and a local colleague are
submitting a proposal to give a 1/2-day tutorial on OE/yocto at this
year's ottawa linux symposium:
http://www.linuxsymposium.org/2012/
and my plan is to start from the absolute basics and walk attendees
through the really simple o
Hi,
I guess we can just put that in the docs for now. For future improvement
> though I wonder if we can trick the fetcher into just pulling across the
> current files into the rootfs. I'll put that on my todo list for later.
>
The following thread suggest a patch to fix it:
http://sourceforge.
Patch 1 and 2 look fine, but I have questions on this one
On 3/27/12 2:51 PM, Christopher Larson wrote:
From: Christopher Larson
This allows setting DEFAULTTUNE to powerpc or powerpc-nf rather than just the
more specific cpu/machine tuning.
Signed-off-by: Christopher Larson
---
meta/conf
On Tuesday 27 March 2012 11:16:10 Saul Wold wrote:
> Yes, there is an issue with genext2fs needing memory to build the
> filesystem first. I noted in another email thread that the Debian build
> system had so resort to dd, mkfs.ext3, mounting and copying. The issue
> with that is that it requires
From: Christopher Larson
This allows setting DEFAULTTUNE to powerpc or powerpc-nf rather than just the
more specific cpu/machine tuning.
Signed-off-by: Christopher Larson
---
meta/conf/machine/include/powerpc/arch-powerpc.inc |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --
From: Christopher Larson
Use of FPRs instead of GPRs is incompatible with e500/SPE, so let's be
explicit about the use of GPRs to avoid potential errors. For example, with
the Sourcery G++ toolchain, one can hit: conftest.c:1:0: error: E500 and FPRs
not supported.
Signed-off-by: Christopher Lars
From: Christopher Larson
This ensures we get the files from the correct multilib dir in the external
toolchain when using powerpc with soft-float.
Signed-off-by: Christopher Larson
---
meta/conf/distro/include/tcmode-external-csl.inc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
On Mon, Mar 26, 2012 at 7:24 PM, Xiaofeng Yan
wrote:
> From: Xiaofeng Yan
>
> User can use these variables to get atchiving packages they want.
>
> Signed-off-by: Xiaofeng Yan
> ---
> meta-yocto/conf/local.conf.sample.extended | 32
>
> 1 files changed, 32 insert
On Tuesday 27 March 2012 08:20:11 Robert P. J. Day wrote:
> i'm currently poring over the OE docs (including the ones at the
> yocto site), and i'm trying to figure out how to simply add a package
> to an image through one's local.conf file.
>
> the current yocto ref manual has an entire secti
On Tue, 27 Mar 2012, Marko Katić wrote:
> I haven't tried this myself on images, but you can probably use
> .bbappend for this. I think bbappend files provide a proper way for
> extending recipes. So for instance,if you want to add a package to
> the core-image-minimal image you would place the fo
On 03/27/2012 07:37 AM, Paul Eggleton wrote:
On Monday 26 March 2012 22:42:54 Saul Wold wrote:
Updated comments per Darren's request, added cleanup to
image-types to only use one -i (inode-count) parameter.
I tried this series on my build machine, but do_rootfs failed with "genext2fs:
not enou
Hi,
some more stupid questions:
What causes a variable being global (accessible by all recipes)?
Does the declaration in *.conf lead to global variable?
Are there other mechanisms forcing global scope?
Thanks in advance
Andreas
___
Openembedded-core
On Tue, Mar 27, 2012 at 09:49:36PM +0800, Robert Yang wrote:
>
>
> On 03/27/2012 09:35 PM, Martin Jansa wrote:
> > On Tue, Mar 27, 2012 at 09:28:09PM +0800, Robert Yang wrote:
> >>
> >> Hi Martin,
> >>
> >> Thanks for reporting this, and I'm very sorry for the inconvenience,
> >> please see my co
On Monday 26 March 2012 22:42:54 Saul Wold wrote:
> Updated comments per Darren's request, added cleanup to
> image-types to only use one -i (inode-count) parameter.
I tried this series on my build machine, but do_rootfs failed with "genext2fs:
not enough memory for filesystem".
The machine has
On 03/27/2012 09:35 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 09:28:09PM +0800, Robert Yang wrote:
Hi Martin,
Thanks for reporting this, and I'm very sorry for the inconvenience,
please see my comment inline ...
On 03/27/2012 07:33 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 01:0
On 03/27/2012 09:35 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 09:28:09PM +0800, Robert Yang wrote:
Hi Martin,
Thanks for reporting this, and I'm very sorry for the inconvenience,
please see my comment inline ...
On 03/27/2012 07:33 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 01:0
On Tue, Mar 27, 2012 at 09:28:09PM +0800, Robert Yang wrote:
>
> Hi Martin,
>
> Thanks for reporting this, and I'm very sorry for the inconvenience,
> please see my comment inline ...
>
> On 03/27/2012 07:33 PM, Martin Jansa wrote:
> > On Tue, Mar 27, 2012 at 01:06:33PM +0200, Martin Jansa wrote
Hi Martin,
Thanks for reporting this, and I'm very sorry for the inconvenience,
please see my comment inline ...
On 03/27/2012 07:33 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 01:06:33PM +0200, Martin Jansa wrote:
On Fri, Feb 24, 2012 at 12:01:37AM +, g...@git.openembedded.org wrote:
On Tuesday 27 March 2012 15:08:28 Andreas Oberritter wrote:
> On 27.03.2012 13:50, Paul Eggleton wrote:
> > +PSEUDOBINDIR=`bitbake -e | grep STAGING_BINDIR_NATIVE=\" | cut -d
> > '=' -f2 | cut -d '"' -f2`
> I think using sed might improve readability:
>
> bitbake -e | grep ^STAGING_BINDIR_
On 27.03.2012 13:50, Paul Eggleton wrote:
> Add some comments explaining what this script does, fix one grammatical
> error in a comment and make the tar-replacement-native comment give the
> full reason why it is needed.
>
> Signed-off-by: Paul Eggleton
Acked-by: Andreas Oberritter
> ---
> s
On 27.03.2012 13:50, Paul Eggleton wrote:
> The recent addition of the check to ensure the user was in their build
> directory disabled the ability to switch between build directories
> without re-running the build environment setup script. We can rely
> upon checking for conf/bblayers.conf instead
On 27.03.2012 13:50, Paul Eggleton wrote:
> If pseudodone doesn't exist, we can get STAGING_BINDIR_NATIVE by calling
> bitbake -e and use that as the path to check for pseudo before we give
> up and try to build it explicitly first.
>
> This is useful for people who share TMPDIR between multiple b
I haven't tried this myself on images, but you can probably use .bbappend
for this. I think bbappend files provide a proper way for extending
recipes. So for instance,
if you want to add a package to the core-image-minimal image you would
place the following in your core-image-minimal.bbappend file
i'm currently poring over the OE docs (including the ones at the
yocto site), and i'm trying to figure out how to simply add a package
to an image through one's local.conf file.
the current yocto ref manual has an entire section about customizing
images:
http://www.yoctoproject.org/docs/curr
The recent addition of the check to ensure the user was in their build
directory disabled the ability to switch between build directories
without re-running the build environment setup script. We can rely
upon checking for conf/bblayers.conf instead, so use this check.
This does allow BUILDDIR (wh
Add some comments explaining what this script does, fix one grammatical
error in a comment and make the tar-replacement-native comment give the
full reason why it is needed.
Signed-off-by: Paul Eggleton
---
scripts/bitbake | 16 +---
1 files changed, 13 insertions(+), 3 deletions(-
If pseudodone doesn't exist, we can get STAGING_BINDIR_NATIVE by calling
bitbake -e and use that as the path to check for pseudo before we give
up and try to build it explicitly first.
This is useful for people who share TMPDIR between multiple build
directories.
Signed-off-by: Paul Eggleton
---
Andreas, if you could review these that would be much appreciated.
The following changes since commit 644b7503c37fd73730dd3d7841463b158b8934ed:
guile: Deal with hardcoded path issues (2012-03-27 00:28:41 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-
On Tue, Mar 27, 2012 at 01:06:33PM +0200, Martin Jansa wrote:
> On Fri, Feb 24, 2012 at 12:01:37AM +, g...@git.openembedded.org wrote:
> > Module: openembedded-core.git
> > Branch: master
> > Commit: 7c99ef6d2173b14e1109a540ee5ae47b56d707e7
> > URL:
> > http://git.openembedded.org/?p=openem
On Fri, Feb 24, 2012 at 12:01:37AM +, g...@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 7c99ef6d2173b14e1109a540ee5ae47b56d707e7
> URL:
> http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=7c99ef6d2173b14e1109a540ee5ae47b56d707e7
>
> A
nspr failed to build on x86_64 board(e.g., qemux86-64):
x86_64-poky-linux-gcc-m64 ... -m32 ...
...
fatal error: gnu/stubs-32.h: No such file or directory
This is because there are both '-m64' and '-m32' in gcc's options, and
the later one is used, but what we need is '-m64' since it is x86_64
* The test info, tested on:
-> The hosts are:
Fedora 16 64bit, Ubuntu 10.10 32bit
-> The MACHINEs are:
qemux86, qemux86-64 and qemuarm
// Robert
The following changes since commit d3e0beed9eef53018158c9f999cd20b44629aa61:
guile: Deal with hardcoded path issues (2012-03-27 00:29:0
The following changes since commit d3e0beed9eef53018158c9f999cd20b44629aa61:
guile: Deal with hardcoded path issues (2012-03-27 00:29:00 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/contacts
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=
Install schema should respect to GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL,
If GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL is set, the schema should not
be installed, but it always installed shema before, this was incorrect
and it would cause host contamination since it would read
$HOME/gconf/.gconf.
[YOCTO
contacts_0.9.bb failed to build since lacks of:
* SRC_URI[md5sum] or SRC_URI[sha256sum]
* LIC_FILES_CHKSUM
And an indent error in Makefile.am.
Fix these problems at the moment, maybe we should remove this old
version recipe since there is a contacts_git.bb
[YOCTO #2178]
Signed-off-by: Robert Y
64 matches
Mail list logo
