Is there a kernel-devicetree package in you tmp/deploy ?
I'm using ipk and I have:
tmp/deploy/ipk/syrcxx/kernel-devicetree_2.6.38-r4_syrcxx.ipk
If it is not there that is your problem.
You may also want to nuke your tmp dir and rebuild (with sstate it should
not take excessively long)
Frans
20
3 at 9:24 AM, Frans Meulenbroeks
> wrote:
> > There is also a default base_do_install() that is empty.
> > Wouldn't it be more logical if the base_do_install would read:
> >
> > Currently people using only base, need to add a do_install to their
> recipe
>
Hi!
Apologies upfront if this is the wrong list. I'm not always sure when
things should go to the yocto list and when to oe-core.
Anyway, my question/issue with danny.
In base.bbclass I see a default base_do_compile that reads:
base_do_compile() {
if [ -e Makefile -o -e makefile -o -e GNUma
2012/7/30 Bruce Ashfield
> On 12-07-30 10:20 AM, Frans Meulenbroeks wrote:
>
>> Hi Bruce,
>>
>> Thanks for your support.
>> See below
>>
>> 2012/7/30 Bruce Ashfield > <mailto:bruce.ashfield@gmail.**com >>
>>
&
2012/7/30 Bruce Ashfield
> On 12-07-30 10:20 AM, Frans Meulenbroeks wrote:
>
>> Hi Bruce,
>>
>> Thanks for your support.
>> See below
>>
>> 2012/7/30 Bruce Ashfield > <mailto:bruce.ashfield@gmail.**com >>
>>
&
Hi Bruce,
Thanks for your support.
See below
2012/7/30 Bruce Ashfield
> On Mon, Jul 30, 2012 at 7:33 AM, Frans Meulenbroeks
> wrote:
> > Dear all,
> >
> > I finally managed to find time to pick up porting my project to denzil
> and
> > did encounter two is
Dear all,
I finally managed to find time to pick up porting my project to denzil and
did encounter two issues that I wanted to report back:
First is that I could not find what the preferred way was to disable a
kernel option in my bsp.
(the option concerned is CONFIG_PM).
Of course I can sed it o
Bjorn, these are some interesting ideas.
Some feedback below.
This is from the perspective of asomeone who develops for embedded systems
boards
2012/6/14 Björn Stenberg
> Hi.
>
> Many source packages include their own package test suites. We are looking
> at running these tests on target in a st
2012/5/11 Bruce Ashfield :
> On 12-05-11 08:51 AM, Frans Meulenbroeks wrote:
>>
>> 2012/5/11 Bruce Ashfield:
>>>
>>> On 12-05-11 03:07 AM, Frans Meulenbroeks wrote:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I'm
2012/5/11 Bruce Ashfield :
> On 12-05-11 03:07 AM, Frans Meulenbroeks wrote:
>>
>> Hi,
>>
>> I'm wondering how to do a kernel rebuild after doing changing the .config
>> using
>> bitbake -c menuconfig virtual/kernel
>> I've tried forcing a
Hi,
I'm wondering how to do a kernel rebuild after doing changing the .config using
bitbake -c menuconfig virtual/kernel
I've tried forcing a recompile using:
bitbake -ccompile -f virtual/kernel
that indeed rebuilds the kernel
However if I then do a bitbake virtual/kernel this does not result in
a
2012/5/9 Bruce Ashfield :
> On 12-05-09 10:11 AM, Frans Meulenbroeks wrote:
>>
>>
>>
>> Bruce, thanks a lot for your help! Greatly appreciated!
>>
>> I've verified this at work and noticed that things are not exactly
>> working as expected (alt
2012/5/8 Bruce Ashfield :
> On 12-05-08 09:03 AM, Frans Meulenbroeks wrote:
>>
>> 2012/5/8 Bruce Ashfield:
>>>
>>> On 12-05-08 03:18 AM, Frans Meulenbroeks wrote:
>>>>
>>>>
>>>> 2012/5/7 Bruce Ashfi
2012/5/8 Flanagan, Elizabeth :
>>
>> Something missing?
>> And what is the best way to find out what licenses are used?
>
> tmp/deploy/${IMAGE}/license.manifest
>
> I have a bug open to document the license infrastructure.
Elizabeth, thanks for your reply.
I peeked in my tree, actually it seems t
2012/5/9 Yes Yanus :
>
>
> If you use archiver.bbclass , you should enable three variables
> INHERIT += "archive-original-source"
> SOURCE_ARCHIVE_PACKAGE_TYPE = 'srpm' or 'tar'
> SOURCE_ARCHIVE_LOG_WITH_SCRIPTS ?= 'logs_with_scripts' or 'logs'
>
Thanks. I'll try that.
Originally I had only INHE
2012/5/8 Saul Wold :
> On 05/08/2012 03:29 AM, Frans Meulenbroeks wrote:
>>
>> 2012/5/8 Frans Meulenbroeks:
>>>
>>> 2012/5/8 Frans Meulenbroeks:
>>>>
>>>> Dear all,
>>>>
>>>> A next question/issue wrt my denzil experi
2012/5/8 Bruce Ashfield :
> On 12-05-08 03:18 AM, Frans Meulenbroeks wrote:
>>
>> 2012/5/7 Bruce Ashfield:
>>>
>>> On 12-05-07 03:29 PM, Frans Meulenbroeks wrote:
>>>>
>>>>
>>>> 2012/5/7 Bruce Ashfi
2012/5/8 Jim Kosem :
> Hi,
>
> We in the Yocto London team have put together user requirements and ideas
> around what we think Web Hob should be.
>
> https://wiki.yoctoproject.org/wiki/Yocto_Webhob_1.3
>
> Any contributions, help and comments are appreciated.
>
> Thanks.
>
> - Jim Kosem
Jim,
I'm
2012/5/8 Frans Meulenbroeks :
> 2012/5/8 Frans Meulenbroeks :
>> Dear all,
>>
>> A next question/issue wrt my denzil experiment:
>>
>> I wanted to know what licenses are used in my image.
>> I found tmp/deploy/licenses but this is package oriented and d
2012/5/8 Frans Meulenbroeks :
> Dear all,
>
> A next question/issue wrt my denzil experiment:
>
> I wanted to know what licenses are used in my image.
> I found tmp/deploy/licenses but this is package oriented and does not
> really give a quick overview.
>
> The manual g
Dear all,
A next question/issue wrt my denzil experiment:
I wanted to know what licenses are used in my image.
I found tmp/deploy/licenses but this is package oriented and does not
really give a quick overview.
The manual gave me this section:
http://www.yoctoproject.org/docs/current/poky-ref-ma
2012/5/7 Bruce Ashfield :
> On 12-05-07 03:29 PM, Frans Meulenbroeks wrote:
>>
>> 2012/5/7 Bruce Ashfield:
>>>
>>> On 12-05-07 10:41 AM, Frans Meulenbroeks wrote:
>>>>
>>>>
>>>> Hi all,
>>>>
>>>
2012/5/7 Bruce Ashfield :
> On 12-05-07 10:41 AM, Frans Meulenbroeks wrote:
>>
>> Hi all,
>>
>> Not sure what the best place is to mail this (the YP list or oe-core
>> or oe-devel or ...)
>> Apologies if this is the wrong place.
>>
>> The prob
Hi all,
Not sure what the best place is to mail this (the YP list or oe-core
or oe-devel or ...)
Apologies if this is the wrong place.
The problem I'm facing is the following:
I have a kernel with some additional drivers that are not upstreamed
because they are very specifc.
I'm moving from oe-cl
Already mentioned this yesterday in the channel, but was not picked up.
the channel topic could be changed to refer to 1.2 i.s.o. 1.1
not sure who has the powers to do so.
Have fun, Frnas
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctop
Dear all,
I'm migrating a project from oe-classic to yocto 1.2.
This goes fairly smoothly. Got some warnings I reported before.
If I build my app it runs fine (with the uclibc from oe-classic that
is already on the board).
Next step was to try to build a complete image.
There I encountered two i
Dear all,
I have build core-image-minimal with yocto 1.2
Worked quite nice, but it did give 10 warnings
Four of these were non-fetchers:
WARNING: Failed to fetch URL
http://kernel.org/pub/linux/kernel/people/jsipek/guilt/guilt-0.33.tar.gz
WARNING: Failed to fetch URL
http://kernel.org/pub/linux/u
2012/5/1 Mark Hatle :
[...]
>
> Once you have verified that the e300c3 binaries are functional, please send
> a your updated tune to the oe-core list... or if you prefer send it to me
> and I can review it and submit it (with your permission) to the oe-core
> list.
>
> I'm interested in keeping t
2012/5/1 Tom Zanussi :
> Hi Frans,
>
> Thanks for your input, comments below...
>
> On Tue, 2012-05-01 at 16:21 +0200, Frans Meulenbroeks wrote:
>> Dear all,
>>
>> In this email I'd like to share my experiences wrt creating a new bsp.
>> I hope this is u
2012/5/1 Khem Raj :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/01/2012 07:21 AM, Frans Meulenbroeks wrote:
>
>>
>> Tried to use yocto-bsp with the standard 7.0 setup (where there is
>> a poky-denzil-7.0-build dir adjacent to the soruce dir). yoc
Dear all,
In this email I'd like to share my experiences wrt creating a new bsp.
I hope this is useful for someone (e.g. for updating the doc). Feel
free to point out the n00bish errors I made, or where I could have
improved.
Aim was to bring my current board (powerpc mpc8313e based) onto yocto 1
Yocto team,
Thanks for making this happen & congrats with the release.
As our next project might be yocto based (moving from oe-classic), I
decided to give it a spin right away and noticed one tiny thing
I peeked at
http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
Reading the discussion, I was wondering whether something under the
yocto umbrella should be self-contained layerwise.
E.g. would it be ok to depend on an external meta-whatsoever?
If so, this does have some quality implications, especially if the
external repo has higher prio and contains alterna
2012/1/30
> Hi,
>
> I am investigating Yocto for a build system here. Part of my requirements
> for a build system is auditable/traceable builds that can be replicated
> long into the future (our company has a 10 year warranty on our products,
> and we build products for the multidecade term). In
2011/2/14 Darren Hart
> On 02/13/2011 01:27 PM, Frans Meulenbroeks wrote:
>
>> Hi,
>>
>> I got one of the blacksand boards with N450 that were given away at
>> the ELC, and I am wondering if there happens to be a bios upgrade for
>> it (or at least make t
2011/5/3 Richard Purdie
> On Tue, 2011-05-03 at 22:05 +0200, Frans Meulenbroeks wrote:
> > 2011/5/3 Philip Balister
> >
> > [...]
> >
> > People ask me why they should join the eV. Besides being a
> > good way to show your support for th
2011/5/3 Philip Balister
[...]
>
> People ask me why they should join the eV. Besides being a good way to show
> your support for the OpenEmbedded project, the Technical Steering Committee
> is elected by the eV members.
>
> Sorry but the current TSC is NOT elected by the eV members.
Actually t
Hi,
I got one of the blacksand boards with N450 that were given away at
the ELC, and I am wondering if there happens to be a bios upgrade for
it (or at least make the bios a little bit less chatty and faster
starting).
Anyone any idea?
Thanks! Frans
___
2010/12/16 Saul Wold :
>
> Hello All,
>
> Recently Richard sent around an email proposing that a new repository be
> created for hosting layers that are not part of the core Yocto Metadata.
>
> This new repository "poky-extras" can host different contributed layers and
> will be open to any one.
>
Cool.
Thanks a lot!
Would this also be the place where user contributed bsp's (like the
one for kirkwood I posted a while ago) could go in?
Frans
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Dear all.
Is AUTOTOOLS_STAGE_PKGCONFIG still of any use?
I was trying to fidn out what I did, I ran a grep on both my
openembedded dir (results see below) and my yocto tree, both trees at
git head.
I see a lot of places where it is set but no place where it is used.
Anyone who can confirm that th
Hi,
I was porting a recipe from OE to yocto and bumped into a
LIC_FILES_CHKSUM error.
I get a message about LIC_FILES_CHKSUM
Checked the ref man
(http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-specifying-LIC_FILES_CHKSUM)
added this:
LIC_FILES_CHKSUM = "file://C
take every once in a while).
Frans.
-- Forwarded message --
From: Bruce Ashfield
Date: 2010/11/29
Subject: Re: [yocto] [PATCH] meta-bsp-kirkwood: created layer for
Marvellkirkwood
To: Frans Meulenbroeks
On 10-11-29 03:30 PM, Frans Meulenbroeks wrote:
>
> 2010/11/2
I was trying to create a bsp layer. In the doc I bumped into the
following example for layer.conf:
# We have a conf directory, add to BBPATH
BBPATH := "${BBPATH}${LAYERDIR}"
[...]
Isn't there a colon mssing here.
If I look at the layer.conf of meta-ememlow it does have a colon:
BBPATH := "${BBP
Kevin, Mark,
Thanks for yoru support.
I'll try to nuke the packaging stamps tonight to see if that helps,
otherwise I guess it'll be a complete rebuild.
Wrt timing: I'll wait for the solution. I hope the parallel parsing
patches from Chris Larson will also make it into poky/yocto soon.
Frans
___
2010/11/24 Mark Hatle :
> The files in question would be tmp/deploy/rpm/mips/rpm-5.1.10-r7.mips.rpm (or
> similar)
>
> That should exist.. If it doesn't something went wrong with the build of the
> package.
>
> If it does, look in the directory (that has the RPM package) for a directory
> called
Mark, thanks for your reply!
2010/11/24 Mark Hatle :
> On 11/24/10 1:36 PM, Frans Meulenbroeks wrote:
>> I was trying to build poky-image-minimal (git head of nov 20).
>> | Processing task-poky-boot...
>> | Processing rpm...
>> | Unable to find package rpm!
>>
I was trying to build poky-image-minimal (git head of nov 20).
Host: opensuse 11.2
target: sheevaplug (I added the machine config and kernel from openembedded)
However creating the rootfs fails because it is unable to find package rpm
| Generating solve db for /home/frans/poky/poky/build/tmp/deplo
2010/11/19 Richard Purdie :
> On Fri, 2010-11-19 at 10:42 +0100, Frans Meulenbroeks wrote:
>> 2010/11/19 Tian, Kevin :
>>
>> The same also holds if you want to keep two versions because they are
>> e.g. functionwise very different.
>> Sometimes this is already do
2010/11/19 Tian, Kevin :
>>From: Frans Meulenbroeks
>>Sent: Friday, November 19, 2010 4:45 PM
>>
>>Dear all,
>>
>>Peeking at flex I was wondering whether we should try to avoid using
>>.inc files in recipes especially if there is only one recipe.
>>
2010/11/19 Gary Thomas :
>
> The fact that there is only one recipe using a particular .inc is (I
> believe)
> a Poky/Yocto design practice. Once a given recipe is known to work and
> cause
> no other dependencies or regressions, older versions are purged. This is
> how
> Poky can build a very u
Dear all,
Peeking at flex I was wondering whether we should try to avoid using
.inc files in recipes especially if there is only one recipe.
flex has:
fr...@frans-desktop:~/yocto/poky-laverne-4.0$ ls meta/recipes-devtools/flex
flex_2.5.35.bb flex.inc
Here the inc file could be merged into the b
2010/11/6 Saul Wold :
>
> Please find enclosed the annotated list of recipes that are not currently
> built as part of any task or image. There are a some basic options that
> could occur with these recipes, do nothing, move the recipe to a layer, or
> add the recipe to an existing image. The notes
53 matches
Mail list logo
