date:20120621

Hi Saul,

Thanks for explaining. But I must say: to an outsider, the existing naming
does not explain how these 2 things relate to each other.

We are adding a description of the 'self-hosted-image' to Hob, including a
link to the Build Appliance page in the Yocto Project website. But I am
not sure it will be enough to fully explain the relationship between both.
Is there any reason why the recipe and the ovf file need to have different
names?

Cheers

Belen

On 20/06/2012 17:44, "Saul Wold"  wrote:

>On 06/20/2012 09:23 AM, Barros Pena, Belen wrote:
>> Does anybody know why are we calling it 'self-hosted-image' in Hob and
>> 'build-appliance' in the Yocto Project website? Wouldn't it be easier if
>> we used the same name everywhere? Which one should be used?
>>
>They are slightly different.  The self-hosted-image is the recipe name
>that generates the image.  The build-appliance is the VMware OVF file
>and bits needed to use VMPlayer or VMWorkstation.  The self-hosted-image
>is the underlying disk image used in the Build Appliance
>
>Sau!
>
>> Thanks!
>>
>> Belen
>>
>> -
>> Intel Corporation (UK) Limited
>> Registered No. 1134945 (England)
>> Registered Office: Pipers Way, Swindon SN3 1RJ
>> VAT No: 860 2173 47
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Selecting base images in Hob

Thanks!

I'll move core-image-core to the stripped-down group.

We don't need to enforce a one to one relationship between images and
groups: an image could be in more than one group, so we could also create
a 'for development' group with all the sdk and dev images.

Any other suggestions on how to group the existing base images?

Cheers

Belen

On 20/06/2012 18:19, "Khem Raj"  wrote:

>On Wed, Jun 20, 2012 at 9:17 AM, Barros Pena, Belen
> wrote:
>> In Hob, we use a drop-down list to select your image. But with 19 base
>> images now available, we have already outgrown the capacity of this UI
>> widget (the guidelines recommend using them when you have between 3 and
>>10
>> items). I filed bug 2345 (nice number) to look at alternative ways of
>> presenting and selecting base images in Hob.
>>
>>
>> The solution I am looking at is based on grouping the base images. I
>> thought I might ask for some help from the list to create those groups.
>> This is what I've come up with:
>>
>> Group 1: Stripped-down images. It includes:
>>
>> core-image-base
>> core-image-basic
>> core-image-minimal
>> core-image-minimal-dev
>> core-image-minimal-initramfs
>> core-image-minimal-mtdutils
>>
>> Group 2: GUI images. It includes:
>>
>> core-image-clutter
>> core-image-core
>
>core-image-core is a console image so prolly move it to above group.
>
>> core-image-sato
>> core-image-sato-dev
>> core-image-sato-sdk
>> qt4e-demo-image
>>
>> Group 3: LSB-conforming. It includes:
>>
>> core-image-lsb
>> core-image-lsb-dev
>> core-image-lsb-sdk
>>
>> Group 4: For real-time use. It includes:
>>
>> core-image-rt
>> core-image-rt-sdk
>>
>> Group 5 is just the self-hosted-image
>>
>> Group 6 would be the 'Create you own image' option
>>
>> Any suggestions on how to better group these images and recommendations
>>on
>> how to name the groups would be very welcome.
>
>may be all dev/sdk images can be grouped together ?
>current grouping is nice though
>
>>
>>
>> Thanks!
>>
>> Belen
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -
>> Intel Corporation (UK) Limited
>> Registered No. 1134945 (England)
>> Registered Office: Pipers Way, Swindon SN3 1RJ
>> VAT No: 860 2173 47
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] self-hosted image vs. build appliance

Thanks, Dave. If no suggestions come in, I'll file the bug.

Belen

On 20/06/2012 23:16, "Stewart, David C"  wrote:

>
>>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>boun...@yoctoproject.org] On Behalf Of Barros Pena, Belen
>>Sent: Wednesday, June 20, 2012 9:24 AM
>>
>>Does anybody know why are we calling it 'self-hosted-image' in Hob and
>>'build-appliance' in the Yocto Project website? Wouldn't it be easier if
>>we used the same name everywhere? Which one should be used?
>
>Yes indeed, we should have consistent naming for this feature.
>
>The problem is, neither name is very good.
>
>"build-appliance" = an implication that the thing "just works" like an
>appliance should just work in your kitchen. Unfortunately, the name isn't
>very descriptive.
>"Self-hosted-image" = a description of how the thing is constructed (it's
>a Linux OS which was constructed by the Yocto Project itself, and it
>builds using the Yocto Project).
>
>So neither name is good, but build appliance is usually the one I use.
>
>If anyone has a better name I WOULD LOVE TO HAVE IT. Otherwise please
>file a bug to change the self-hosted-image name to build appliance.
>
>Dave

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 答复: Web HOB planning discussion

Thanks, Xiaotong.

I don't think features 1 and 3 are critical, but I think we will need to
find a technical solution for point 2.

Cheers

Belen

On 21/06/2012 06:19, "Lv, XiaotongX"  wrote:

>About Jim’s video requirement.  and many users to many bitbake servers
>mapping. maybe there are some problems maybe to solve.
>
>Some my questions:
>1. running builds remaining time. difficult to estimate.
>  when a user check all the builds status, whether they are done or not.
>  the remaining time, it is difficult to estimate. cause in bitbake
>server. I donot accurately
>  to know current build when it starts, how long it will finish for this
>build.
>  so to give an accurate remaining time for user. it is difficult.
>2. Add users own layers. how to implement?
>  one user wanna to add own layers. so he uploads own layer by browser to
>put in web server firstly.
>  then we need let web server do one thing. to copy the layer to bitbake
>server.
>  so my problem. 
>  1).if user upload a unavailable compression layer folder. how to check
>the folder whether it is
>a real layer or not. If it is hack shells or hack software. How to
>deal with it?
>  2).if user next operation is time out during building, for example,
>after building package,
>User donot select package to build image for long time, so system
>will trigger a time out event to stop and cancel this build .
>next time, we need to assign a new bitbake for this user.
>in fact. user only wanna to continue his operation based on last time
>build. Donot need a new bitbake sever to repeat build.
>And now all of user build, we only use one build directory. So it is
>difficult to remain last different users build status.
>  
>3.after build completed in browser. it is difficult to test and deploy
>image directly. how to solve these problems?
>we only can download and upload files in browser. We cannot write or read
>a local machine files and do some operation in browser.
>So to test and deploy images by browser. It is difficult. So maybe we
>need to develop a single client to solve this problem.
>But we know. If develop a client. Whether we satisfy different OS. For
>example, window xp, window 7, linux different version, mac os.
>
>
>
>发件人: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] 代表
>Barros Pena, Belen [belen.barros.p...@intel.com]
>发送时间: 2012年6月14日 16:37
>到: Osier-mixon, Jeffrey; Stewart, David C
>Cc: Jim Kosem; yocto@yoctoproject.org; Konstantinos Papagiannopoulos
>主题: Re: [yocto] Web HOB planning discussion
>
>Hi all,
>
>Thanks for the feedback: loads of interesting stuff there. We'll keep it
>all in mind when working on the next iteration.
>
>If you think of anything else, please post it here.
>
>Cheers
>
>Belen
>
>From: , Jeffrey
>mailto:jeffrey.osier-mi...@intel.com>>
>Date: Wednesday, 13 June 2012 19:00
>To: "Stewart, David C"
>mailto:david.c.stew...@intel.com>>
>Cc: Konstantinos Papagiannopoulos
>mailto:he...@konputer.net>>,
>"yocto@yoctoproject.org"
>mailto:yocto@yoctoproject.org>>, Jim Kosem
>mailto:j...@halfman.com>>
>Subject: Re: [yocto] Web HOB planning discussion
>
>I agree, it is looking really interesting. Some comments below.
>
>On Wed, Jun 13, 2012 at 10:39 AM, Stewart, David C
>mailto:david.c.stew...@intel.com>> wrote:
>* This could be a great way for an organization to implement a workflow
>process using YP, rather than try to invent one themselves. We have
>gotten the feedback that some larger organizations want something like
>this, so I'm pleased with that direction.
>
>Agreed - I have fielded a few questions about this as well
>
>* With the above in mind, a key meta-usage is installing and configuring
>the server. For example, I could imagine an organization wanting to
>easily customize the home page with their own news and design
>information, etc.
>
>* I could also see the opportunity for an OSV or service provider to
>brand the interface with their own goodness and extending it with their
>own features so this might be another meta-usage.
>
>* And while I'm on a roll... whenever we talk about how the administrator
>installs this, we need consider how they update from a previous version,
>particularly if they have customized the home screen or other bits.
>
>If branding & customization happen in CSS, the whole customization part
>should be portable from one version to another (as long as no one breaks
>anything structural). If we want to enable customization of
>functionality, though - e.g. pre-filter package selection, restrict
>certain features... - I could see that being tricky to implement in a
>portable way.
>
>* Project creation and member add/remove should perhaps be an
>administrator role and password protected?
>
>I vote yes on user management, but why password-protect project creation?
>
>Other thoughts:
>
>My feeling is that both Hob and WebHob will be most useful as tools to
>get people started. At some point, anyo

Re: [yocto] Dependency Tree

2012-06-21 Thread Paul Eggleton

On Wednesday 20 June 2012 16:28:02 Jim Rucker wrote:
> Thanks for the help
> "how did you conclude that its a prerequisite with external toolchain and
> not with internal toolchain?"
> Because this system doesn't have network access, so I have to transfer
> files to the system manually and use the PREMIRROR feature. When I build
> using the internal toolchain I never needed to grab qemu.
> Side note- after researching this it looks like qemu was needed for
> localization files required by eglibc, while the internal gcc uses a prebuilt
> localization file.

This is something that has apparently been fixed post-denzil. I think you just 
need to set the following:

GLIBC_INTERNAL_USE_BINARY_LOCALE = "precompiled"
ENABLE_BINARY_LOCALE_GENERATION = ""

> Although I'm able to build without network access on edison, I can't seem
> to get it to work on denzil. I seem to get pretty far, but when I get to a
> git repository, it doesn't seem to work. I have the file
> "git2_git.yoctoproject.org.prelink-cross.git.tar.gz", but it never seems to
> try to access it. Any suggestions?

So this suggests that you don't have the prelink-cross git archive in your 
local mirror (assuming PREMIRRORS is set up to also redirect git URIs); hence 
it is trying to go out to the internet to get it.

By the way, do you have BB_NO_NETWORK = "1" set? If not then you should set 
this in local.conf.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Porting of specific Kernel/Driver into yocto.


From: Darren Hart [darren.h...@intel.com]
Sent: Wednesday, May 23, 2012 11:46 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 05/23/2012 05:39 AM, Om Prakash PAL wrote:
> Hi Bruce,
>
> [ I am using "poky-edison-6.0" ]
> I am able to create my rootfs and uImage but when I flashed these on my board,
> while booting I am getting below Error and console get blocked.
>
> =
> [3.575805] EXT3-fs (mmcblk0p1): using internal journal
> [3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data 
> mode
> [3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
> [3.594268] Freeing init memory: 312K
> INIT: version 2.88 booting
>
> Please wait: booting...
> Starting udev
> Starting Bootlog daemon: bootlogd: cannot deduce real console device
> bootlogd.
> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
> done.
> Fri May 11 11:29:00 UTC 2012
> Running postinst /etc/rpm-postinsts/*.sh...
> ERROR: postinst /etc/rpm-postinsts/*.sh failed.

Does this error repeat if you reboot?
Yes, every time.

> INIT: Entering runlevel: 5
> Starting syslogd/klogd: done
> Stopping Bootlog daemon: bootlogd.
> [9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed
>
> =
> and after that it got stuck, I am not getting console.

How long do you let it sit?

after some time(around 10mins) got this msg;
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

and then console got  stuck.
>
> I am building rootfs/uImage with default toolchain used in yocto.
> Is it problem of toolchain?.
> Should I build with our toolchain( we use CodeSourcery)?.

Nothing above suggests a toolchain problem. You have an error running
the postinst scripts from the various rpm packages. Some instrumentation
in those scripts (and the parent script) would help narrow down where it
is failing.

--
Darren

>
> Best Regards,
> Om Prakash Pal
> 
> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
> Sent: Sunday, May 06, 2012 6:00 PM
> To: Om Prakash PAL
> Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 12-05-06 5:43 AM, Om Prakash PAL wrote:
>> Hi Bruce,
>> I am getting some problem in do_install:
>>
>> NOTE: Running task 1535 of 1710 (ID: 517, 
>> /home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
>>  do_install)
>> NOTE: package 
>> linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task 
>> do_install: Started
>>
>> and I waited for ~15hr to complete task do_install: but not completed and i 
>> am not getting any Errors/warnings.
>> Is there any problem?.
>> I have checked that my vmlinux/uImage/zImage has been created successfully 
>> but rootfs has not been created till now.
>>
>> here is my .bb file that is building my local_kernel.
>>
>> inherit kernel
>> require recipes-kernel/linux/linux-yocto.inc
>>
>> KMACHINE = "dev"
>> YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"
>>
>> KBRANCH = "${KMACHINE}"
>> KMETA = "meta"
>>
>> KSRC_linux_yocto ?= "/home/apallan/yocto/kernel/"
>>
>> SRC_URI = "git://${KSRC_linux_yocto};protocol=file;nocheckout=1"
>> SRC_URI +="file://defconfig"
>>
>> SRCREV="${AUTOREV}"
>> SRCREV_pn-linux-u8500 ="0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383"
>>
>> LINUX_VERSION ?= "3.2"
>> LINUX_VERSION_EXTENSION = "-yoctized-${LINUX_KERNEL_TYPE}"
>> PR = "r10"
>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> COMPATIBLE_MACHINE = "(u8500|qemuarm)"
>>
>> # Functionality flags
>> KERNEL_REVISION_CHECKING=""
>> YOCTO_KERNEL_META_DATA=""
>>
>> require recipes-kernel/linux/linux-tools.inc
>>
>> what should be the problem?.
>
> Anything using linux-yocto has exactly the same packaging semantics as
> other kernels, since they all inherit kernel.bbclass.
>
> Maybe your description sounds familiar to others, and others that might
> have better ideas about what's happening in the packaging backend ?
>
> You don't have any special partitions configured ? You are building
> on a local filesystem ? Is rpm or ipkg being used ? .. these are all
> things that could impact performance (but not really 15 hours worth of
> issues).
>
> Are there any hints in the host system logs, or in the kernels do_install
> log ?
>
> Bruce
>
>>
>> Best Regards,
>> Om Prakash Pal
>> 
>> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
>> Sent: Thursday, May 03, 2012 5:59 PM
>> To: Om Prakash PAL
>> Cc: Bruce Ashfield; yocto@yoctoproject.org
>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>>
>> On 12-05-03 05:24 AM, Om Prakash PAL wrote:
>>> Hi Bruce,
>>> Thanks a lot for your help.
>>> Now I am able t

Re: [yocto] Porting of specific Kernel/Driver into yocto.


From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Monday, May 28, 2012 11:25 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-05-23 08:39 AM, Om Prakash PAL wrote:
> Hi Bruce,
>
> [ I am using "poky-edison-6.0" ]
> I am able to create my rootfs and uImage but when I flashed these on my board,
> while booting I am getting below Error and console get blocked.
>
> =
> [3.575805] EXT3-fs (mmcblk0p1): using internal journal
> [3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data 
> mode
> [3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
> [3.594268] Freeing init memory: 312K
> INIT: version 2.88 booting
>
> Please wait: booting...
> Starting udev
> Starting Bootlog daemon: bootlogd: cannot deduce real console device
> bootlogd.
> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
> done.
> Fri May 11 11:29:00 UTC 2012
> Running postinst /etc/rpm-postinsts/*.sh...
> ERROR: postinst /etc/rpm-postinsts/*.sh failed.
> INIT: Entering runlevel: 5
> Starting syslogd/klogd: done
> Stopping Bootlog daemon: bootlogd.
> [9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed
>
> =
> and after that it got stuck, I am not getting console.
>
> I am building rootfs/uImage with default toolchain used in yocto.
> Is it problem of toolchain?.


>I'm just back from vacation. Is this still an ongoing investigation ? As
>Darren mentioned, nothing in that error log indicates a toolchain problem.
>You'd typically end up with silent boot death, or far more catastrophic
>errors if the toolchain was really at fault here.

>It does sound like startup script issues, but without knowing the exact
>makeup of your rootfs, it's hard to say more.

===>I am just using makeup of "Yocto default rootfs" I am not using my own 
makeup of rootfs.

>Even when the board is stuck, is the networking stack up and responding ?
>i.e. can you ping, or even ssh into the box ?

No, Nothing,
we can not do anyhting. it just got stuck.
any help/idea will be appreciable.

Best Regards,
Om Prakash Pal

>Bruce

> Should I build with our toolchain( we use CodeSourcery)?.
>
> Best Regards,
> Om Prakash Pal
> 
> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
> Sent: Sunday, May 06, 2012 6:00 PM
> To: Om Prakash PAL
> Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 12-05-06 5:43 AM, Om Prakash PAL wrote:
>> Hi Bruce,
>> I am getting some problem in do_install:
>>
>> NOTE: Running task 1535 of 1710 (ID: 517, 
>> /home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
>>  do_install)
>> NOTE: package 
>> linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task 
>> do_install: Started
>>
>> and I waited for ~15hr to complete task do_install: but not completed and i 
>> am not getting any Errors/warnings.
>> Is there any problem?.
>> I have checked that my vmlinux/uImage/zImage has been created successfully 
>> but rootfs has not been created till now.
>>
>> here is my .bb file that is building my local_kernel.
>>
>> inherit kernel
>> require recipes-kernel/linux/linux-yocto.inc
>>
>> KMACHINE = "dev"
>> YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"
>>
>> KBRANCH = "${KMACHINE}"
>> KMETA = "meta"
>>
>> KSRC_linux_yocto ?= "/home/apallan/yocto/kernel/"
>>
>> SRC_URI = "git://${KSRC_linux_yocto};protocol=file;nocheckout=1"
>> SRC_URI +="file://defconfig"
>>
>> SRCREV="${AUTOREV}"
>> SRCREV_pn-linux-u8500 ="0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383"
>>
>> LINUX_VERSION ?= "3.2"
>> LINUX_VERSION_EXTENSION = "-yoctized-${LINUX_KERNEL_TYPE}"
>> PR = "r10"
>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> COMPATIBLE_MACHINE = "(u8500|qemuarm)"
>>
>> # Functionality flags
>> KERNEL_REVISION_CHECKING=""
>> YOCTO_KERNEL_META_DATA=""
>>
>> require recipes-kernel/linux/linux-tools.inc
>>
>> what should be the problem?.
>
> Anything using linux-yocto has exactly the same packaging semantics as
> other kernels, since they all inherit kernel.bbclass.
>
> Maybe your description sounds familiar to others, and others that might
> have better ideas about what's happening in the packaging backend ?
>
> You don't have any special partitions configured ? You are building
> on a local filesystem ? Is rpm or ipkg being used ? .. these are all
> things that could impact performance (but not really 15 hours worth of
> issues).
>
> Are there any hints in the host system logs, or in the kernels do_install
> log ?
>
> Bruce
>
>>
>> Best Regards,
>> Om Prakash Pal
>> 
>> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
>> Sent: Thursday, May 03, 2012 5:59 PM
>> To: O

Re: [yocto] Porting of specific Kernel/Driver into yocto.

2012-06-21 Thread Gary Thomas

On 2012-06-21 06:27, Om Prakash PAL wrote:

From: Darren Hart [darren.h...@intel.com]
Sent: Wednesday, May 23, 2012 11:46 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 05/23/2012 05:39 AM, Om Prakash PAL wrote:

Hi Bruce,

[ I am using "poky-edison-6.0" ]
I am able to create my rootfs and uImage but when I flashed these on my board,
while booting I am getting below Error and console get blocked.

=
[3.575805] EXT3-fs (mmcblk0p1): using internal journal
[3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
[3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
[3.594268] Freeing init memory: 312K
INIT: version 2.88 booting

Please wait: booting...
Starting udev
Starting Bootlog daemon: bootlogd: cannot deduce real console device
bootlogd.
Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
done.
Fri May 11 11:29:00 UTC 2012
Running postinst /etc/rpm-postinsts/*.sh...
ERROR: postinst /etc/rpm-postinsts/*.sh failed.

Does this error repeat if you reboot?
Yes, every time.

What image is being used?  I've seen this with core-image-minimal, but it
goes away when the image is more complex, e.g. core-image-sato.  I believe
the init script is always present even if there are no postinst scripts to run.

INIT: Entering runlevel: 5
Starting syslogd/klogd: done
Stopping Bootlog daemon: bootlogd.
[9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed

=
and after that it got stuck, I am not getting console.

How long do you let it sit?

after some time(around 10mins) got this msg;
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

and then console got  stuck.

What do you have SERIAL_CONSOLE set to in your configuration?

I am building rootfs/uImage with default toolchain used in yocto.
Is it problem of toolchain?.
Should I build with our toolchain( we use CodeSourcery)?.

Nothing above suggests a toolchain problem. You have an error running
the postinst scripts from the various rpm packages. Some instrumentation
in those scripts (and the parent script) would help narrow down where it
is failing.

--
Darren

Best Regards,
Om Prakash Pal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Sunday, May 06, 2012 6:00 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-05-06 5:43 AM, Om Prakash PAL wrote:

Hi Bruce,
I am getting some problem in do_install:

NOTE: Running task 1535 of 1710 (ID: 517, 
/home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
 do_install)
NOTE: package 
linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task 
do_install: Started

and I waited for ~15hr to complete task do_install: but not completed and i am 
not getting any Errors/warnings.
Is there any problem?.
I have checked that my vmlinux/uImage/zImage has been created successfully but 
rootfs has not been created till now.

here is my .bb file that is building my local_kernel.

inherit kernel
require recipes-kernel/linux/linux-yocto.inc

KMACHINE = "dev"
YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"

KBRANCH = "${KMACHINE}"
KMETA = "meta"

KSRC_linux_yocto ?= "/home/apallan/yocto/kernel/"

SRC_URI = "git://${KSRC_linux_yocto};protocol=file;nocheckout=1"
SRC_URI +="file://defconfig"

SRCREV="${AUTOREV}"
SRCREV_pn-linux-u8500 ="0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383"

LINUX_VERSION ?= "3.2"
LINUX_VERSION_EXTENSION = "-yoctized-${LINUX_KERNEL_TYPE}"
PR = "r10"
PV = "${LINUX_VERSION}+git${SRCPV}"

COMPATIBLE_MACHINE = "(u8500|qemuarm)"

# Functionality flags
KERNEL_REVISION_CHECKING=""
YOCTO_KERNEL_META_DATA=""

require recipes-kernel/linux/linux-tools.inc

what should be the problem?.

Anything using linux-yocto has exactly the same packaging semantics as
other kernels, since they all inherit kernel.bbclass.

Maybe your description sounds familiar to others, and others that might
have better ideas about what's happening in the packaging backend ?

You don't have any special partitions configured ? You are building
on a local filesystem ? Is rpm or ipkg being used ? .. these are all
things that could impact performance (but not really 15 hours worth of
issues).

Are there any hints in the host system logs, or in the kernels do_install
log ?

Bruce

Best Regards,
Om Prakash Pal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Thursday, May 03, 2012 5:59 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-05-03 05:24 AM, Om Prakash

Re: [yocto] Porting of specific Kernel/Driver into yocto.

Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Gary Thomas
Sent: Thursday, June 21, 2012 6:18 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 2012-06-21 06:27, Om Prakash PAL wrote:
> 
> From: Darren Hart [darren.h...@intel.com]
> Sent: Wednesday, May 23, 2012 11:46 PM
> To: Om Prakash PAL
> Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 05/23/2012 05:39 AM, Om Prakash PAL wrote:
>> Hi Bruce,
>>
>> [ I am using "poky-edison-6.0" ]
>> I am able to create my rootfs and uImage but when I flashed these on my 
>> board,
>> while booting I am getting below Error and console get blocked.
>>
>> =
>> [3.575805] EXT3-fs (mmcblk0p1): using internal journal
>> [3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data 
>> mode
>> [3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
>> [3.594268] Freeing init memory: 312K
>> INIT: version 2.88 booting
>>
>> Please wait: booting...
>> Starting udev
>> Starting Bootlog daemon: bootlogd: cannot deduce real console device
>> bootlogd.
>> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
>> done.
>> Fri May 11 11:29:00 UTC 2012
>> Running postinst /etc/rpm-postinsts/*.sh...
>> ERROR: postinst /etc/rpm-postinsts/*.sh failed.
>
> Does this error repeat if you reboot?
> Yes, every time.

>What image is being used?  I've seen this with core-image-minimal, but it
>goes away when the image is more complex, e.g. core-image-sato.  I believe
>the init script is always present even if there are no postinst scripts to run.

I am also building core-image-minimal.
Is there any problem with this?.
Should I build core-image-sato?.

>
>> INIT: Entering runlevel: 5
>> Starting syslogd/klogd: done
>> Stopping Bootlog daemon: bootlogd.
>> [9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed
>>
>> =
>> and after that it got stuck, I am not getting console.
>
> How long do you let it sit?
>
> after some time(around 10mins) got this msg;
> INIT: Id "1" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel
>
> and then console got  stuck.

>What do you have SERIAL_CONSOLE set to in your configuration?

I have set SERIAL_CONSOLE="115200 ttyAMA2". As we are using ttyAMA2 for console.
>>
>> I am building rootfs/uImage with default toolchain used in yocto.
>> Is it problem of toolchain?.
>> Should I build with our toolchain( we use CodeSourcery)?.
>
> Nothing above suggests a toolchain problem. You have an error running
> the postinst scripts from the various rpm packages. Some instrumentation
> in those scripts (and the parent script) would help narrow down where it
> is failing.
>
> --
> Darren
>
>>
>> Best Regards,
>> Om Prakash Pal
>> 
>> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
>> Sent: Sunday, May 06, 2012 6:00 PM
>> To: Om Prakash PAL
>> Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>>
>> On 12-05-06 5:43 AM, Om Prakash PAL wrote:
>>> Hi Bruce,
>>> I am getting some problem in do_install:
>>>
>>> NOTE: Running task 1535 of 1710 (ID: 517, 
>>> /home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
>>>  do_install)
>>> NOTE: package 
>>> linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task 
>>> do_install: Started
>>>
>>> and I waited for ~15hr to complete task do_install: but not completed and i 
>>> am not getting any Errors/warnings.
>>> Is there any problem?.
>>> I have checked that my vmlinux/uImage/zImage has been created successfully 
>>> but rootfs has not been created till now.
>>>
>>> here is my .bb file that is building my local_kernel.
>>>
>>> inherit kernel
>>> require recipes-kernel/linux/linux-yocto.inc
>>>
>>> KMACHINE = "dev"
>>> YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"
>>>
>>> KBRANCH = "${KMACHINE}"
>>> KMETA = "meta"
>>>
>>> KSRC_linux_yocto ?= "/home/apallan/yocto/kernel/"
>>>
>>> SRC_URI = "git://${KSRC_linux_yocto};protocol=file;nocheckout=1"
>>> SRC_URI +="file://defconfig"
>>>
>>> SRCREV="${AUTOREV}"
>>> SRCREV_pn-linux-u8500 ="0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383"
>>>
>>> LINUX_VERSION ?= "3.2"
>>> LINUX_VERSION_EXTENSION = "-yoctized-${LINUX_KERNEL_TYPE}"
>>> PR = "r10"
>>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> COMPATIBLE_MACHINE = "(u8500|qemuarm)"
>>>
>>> # Functionality flags
>>> KERNEL_REVISION_CHECKING=""
>>> YOCTO_KERNEL_META_DATA=""
>>>
>>> require recipes-kernel/linux/linux-tools.inc
>>>
>>> what should be the problem?.
>>
>> Anything using linux-yocto has exactly the same packaging semantics as
>> other kernels,

Re: [yocto] Porting of specific Kernel/Driver into yocto.

2012-06-21 Thread Gary Thomas

On 2012-06-21 08:16, Om Prakash PAL wrote:

Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Gary Thomas
Sent: Thursday, June 21, 2012 6:18 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 2012-06-21 06:27, Om Prakash PAL wrote:

From: Darren Hart [darren.h...@intel.com]
Sent: Wednesday, May 23, 2012 11:46 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 05/23/2012 05:39 AM, Om Prakash PAL wrote:

Hi Bruce,

[ I am using "poky-edison-6.0" ]
I am able to create my rootfs and uImage but when I flashed these on my board,
while booting I am getting below Error and console get blocked.

=
[3.575805] EXT3-fs (mmcblk0p1): using internal journal
[3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
[3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
[3.594268] Freeing init memory: 312K
INIT: version 2.88 booting

Please wait: booting...
Starting udev
Starting Bootlog daemon: bootlogd: cannot deduce real console device
bootlogd.
Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
done.
Fri May 11 11:29:00 UTC 2012
Running postinst /etc/rpm-postinsts/*.sh...
ERROR: postinst /etc/rpm-postinsts/*.sh failed.

Does this error repeat if you reboot?
Yes, every time.

What image is being used?  I've seen this with core-image-minimal, but it
goes away when the image is more complex, e.g. core-image-sato.  I believe
the init script is always present even if there are no postinst scripts to run.

I am also building core-image-minimal.
Is there any problem with this?.

No.  I think the error message is noise in this case.

Should I build core-image-sato?.

Only if you want/need to - core-image-sato brings in a complete X desktop
environment, maybe not what you're after.

INIT: Entering runlevel: 5
Starting syslogd/klogd: done
Stopping Bootlog daemon: bootlogd.
[9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed

=
and after that it got stuck, I am not getting console.

How long do you let it sit?

after some time(around 10mins) got this msg;
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

and then console got  stuck.

What do you have SERIAL_CONSOLE set to in your configuration?

I have set SERIAL_CONSOLE="115200 ttyAMA2". As we are using ttyAMA2 for console.

What is your target device?  Do you really have /dev/ttyAMA2 serial port??

I am building rootfs/uImage with default toolchain used in yocto.
Is it problem of toolchain?.
Should I build with our toolchain( we use CodeSourcery)?.

Nothing above suggests a toolchain problem. You have an error running
the postinst scripts from the various rpm packages. Some instrumentation
in those scripts (and the parent script) would help narrow down where it
is failing.

--
Darren

Best Regards,
Om Prakash Pal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Sunday, May 06, 2012 6:00 PM
To: Om Prakash PAL
Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-05-06 5:43 AM, Om Prakash PAL wrote:

Hi Bruce,
I am getting some problem in do_install:

NOTE: Running task 1535 of 1710 (ID: 517, 
/home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
 do_install)
NOTE: package 
linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task 
do_install: Started

and I waited for ~15hr to complete task do_install: but not completed and i am 
not getting any Errors/warnings.
Is there any problem?.
I have checked that my vmlinux/uImage/zImage has been created successfully but 
rootfs has not been created till now.

here is my .bb file that is building my local_kernel.

inherit kernel
require recipes-kernel/linux/linux-yocto.inc

KMACHINE = "dev"
YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"

KBRANCH = "${KMACHINE}"
KMETA = "meta"

KSRC_linux_yocto ?= "/home/apallan/yocto/kernel/"

SRC_URI = "git://${KSRC_linux_yocto};protocol=file;nocheckout=1"
SRC_URI +="file://defconfig"

SRCREV="${AUTOREV}"
SRCREV_pn-linux-u8500 ="0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383"

LINUX_VERSION ?= "3.2"
LINUX_VERSION_EXTENSION = "-yoctized-${LINUX_KERNEL_TYPE}"
PR = "r10"
PV = "${LINUX_VERSION}+git${SRCPV}"

COMPATIBLE_MACHINE = "(u8500|qemuarm)"

# Functionality flags
KERNEL_REVISION_CHECKING=""
YOCTO_KERNEL_META_DATA=""

require recipes-kernel/linux/linux-tools.inc

what should be the problem?.

Anything using linux-yocto has exactly the same packaging semantics as
other kernels, since they all inherit kernel.bbclass.

Maybe your descri

[yocto] Hob - proper way to select machine and customer layers

2012-06-21 Thread jfabernathy

So I thought I'd give hob a test. Basically, I wanted to do what I could 
already do with the command line.


Normally, after I set the environment variables, I edit the local.conf 
to change my machine type and parallel processing options. Then I point 
the download directory to a centralized one on my system, and add some 
License statements and some CORE-IMAGE-EXTRA-INSTALL statements for 
extra packages. Then I edit the bblayer.conf to had the path to my layer 
and the meta-intel layers.


To use Hob, I set my environment variable and the just ran hob.  It was 
very slow going through the first 63 packages. I think this is because 
parallel options had not been set and the packages were all being 
downloaded again.  But after I got to the UI of hob, I got errors adding 
my layers to get to the meta-intel layers I wanted.  So I started over 
and edited local.conf and bblayer.conf prior to launching hob.  Now I 
could see my machine from meta-intel, but I could not add my layer in. 
Parsing errors.


Before I report an error, I wanted to see if I have the hob startup 
process right. The issues is around the right way to add 
meta-intel/meta-cedartrail and my personal layer in my home directory.


Any advice?

JIm A

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] self-hosted image vs. build appliance

2012-06-21 Thread Saul Wold


On 06/21/2012 03:30 AM, Barros Pena, Belen wrote:

Hi Saul,

Thanks for explaining. But I must say: to an outsider, the existing naming
does not explain how these 2 things relate to each other.

We are adding a description of the 'self-hosted-image' to Hob, including a
link to the Build Appliance page in the Yocto Project website. But I am
not sure it will be enough to fully explain the relationship between both.
Is there any reason why the recipe and the ovf file need to have different
names?


How about build-appliance-image and building a Build Appliance ovf

Sau!



Cheers

Belen



On 20/06/2012 17:44, "Saul Wold"  wrote:


On 06/20/2012 09:23 AM, Barros Pena, Belen wrote:

Does anybody know why are we calling it 'self-hosted-image' in Hob and
'build-appliance' in the Yocto Project website? Wouldn't it be easier if
we used the same name everywhere? Which one should be used?


They are slightly different.  The self-hosted-image is the recipe name
that generates the image.  The build-appliance is the VMware OVF file
and bits needed to use VMPlayer or VMWorkstation.  The self-hosted-image
is the underlying disk image used in the Build Appliance

Sau!


Thanks!

Belen

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto







___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

Hi,
I just updated my yocto repos and tried a fresh build.

My bblayers.conf file looks like this:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "4"

BBFILES ?= ""
BBLAYERS ?= " \
/tool/yocto/poky/meta \
/tool/yocto/poky/meta-yocto \
/tool/yocto/meta-openembedded/meta-oe \
/tool/yocto/meta-xilinx \
"

And when I run the bitake core-image-minimal;bitbake meta-toolchain I get the
following errors:

$ bitbake core-image-minimal;bitbake meta-toolchain;
Pseudo is not present but is required, building this first before the main build
WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h: file
could not be found | ETA: 00:00:49
WARNING: Unable to get checksum for python-numpy SRC_URI entry numpyconfig.h:
file could not be found
WARNING:
/tool/yocto/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
WARNING: /tool/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it
is recommended to set SYSTEMD_PACKAGES as -systemd
Parsing recipes: 100%
||
Time: 00:00:37
Parsing of 1186 .bb files complete (0 cached, 1186 parsed). 1524 targets, 40
skipped, 0 masked, 0 errors.
WARNING: BBPATH references the current directory, either through an empty
entry, or a '.'.
This is unsafe and means your layer configuration is adding empty
elements to BBPATH.
Please check your layer.conf files and other BBPATH settings to remove
the current working directory references.
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker
(see sanity.conf).
Following is the list of potential problems / advisories:

PATH contains '.' or '', which will break the build, please remove this.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There were 5 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
Pseudo is not present but is required, building this first before the main build
Loading cache: 100%
|##|
ETA: 00:00:00
Loaded 1523 entries from dependency cache.
Parsing recipes: 100%
||
Time: 00:00:07
Parsing of 1186 .bb files complete (1184 cached, 2 parsed). 1524 targets, 40
skipped, 0 masked, 0 errors.
WARNING: BBPATH references the current directory, either through an empty
entry, or a '.'.
This is unsafe and means your layer configuration is adding empty
elements to BBPATH.
Please check your layer.conf files and other BBPATH settings to remove
the current working directory references.
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker
(see sanity.conf).
Following is the list of potential problems / advisories:

PATH contains '.' or '', which will break the build, please remove this.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

Best regards,

Elvis Dowson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Porting of specific Kernel/Driver into yocto.

2012-06-21 Thread McClintock Matthew-B29882

Are you spawning a tty on a non-existent serial port?

-M

On Thu, Jun 21, 2012 at 9:28 AM, Gary Thomas  wrote:
> On 2012-06-21 08:16, Om Prakash PAL wrote:
>>
>> Original Message-
>> From: yocto-boun...@yoctoproject.org
>> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Gary Thomas
>> Sent: Thursday, June 21, 2012 6:18 PM
>> To: yocto@yoctoproject.org
>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>>
>> On 2012-06-21 06:27, Om Prakash PAL wrote:
>>>
>>> 
>>> From: Darren Hart [darren.h...@intel.com]
>>> Sent: Wednesday, May 23, 2012 11:46 PM
>>> To: Om Prakash PAL
>>> Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
>>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>>>
>>> On 05/23/2012 05:39 AM, Om Prakash PAL wrote:

 Hi Bruce,

 [ I am using "poky-edison-6.0" ]
 I am able to create my rootfs and uImage but when I flashed these on my
 board,
 while booting I am getting below Error and console get blocked.

 =
 [    3.575805] EXT3-fs (mmcblk0p1): using internal journal
 [    3.581054] EXT3-fs (mmcblk0p1): mounted filesystem with writeback
 data mode
 [    3.588165] VFS: Mounted root (ext3 filesystem) on device 179:1.
 [    3.594268] Freeing init memory: 312K
 INIT: version 2.88 booting

 Please wait: booting...
 Starting udev
 Starting Bootlog daemon: bootlogd: cannot deduce real console device
 bootlogd.
 Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
 done.
 Fri May 11 11:29:00 UTC 2012
 Running postinst /etc/rpm-postinsts/*.sh...
 ERROR: postinst /etc/rpm-postinsts/*.sh failed.
>>>
>>>
>>> Does this error repeat if you reboot?
>>> Yes, every time.
>>
>>
>>> What image is being used?  I've seen this with core-image-minimal, but it
>>> goes away when the image is more complex, e.g. core-image-sato.  I
>>> believe
>>> the init script is always present even if there are no postinst scripts
>>> to run.
>>
>>
>> I am also building core-image-minimal.
>> Is there any problem with this?.
>
>
> No.  I think the error message is noise in this case.
>
>> Should I build core-image-sato?.
>
>
> Only if you want/need to - core-image-sato brings in a complete X desktop
> environment, maybe not what you're after.
>
>
>>
>>>
 INIT: Entering runlevel: 5
 Starting syslogd/klogd: done
 Stopping Bootlog daemon: bootlogd.
 [    9.737091] av8100_hdmi av8100_hdmi.3: HDMI display probed

 =
 and after that it got stuck, I am not getting console.
>>>
>>>
>>> How long do you let it sit?
>>>
>>> after some time(around 10mins) got this msg;
>>> INIT: Id "1" respawning too fast: disabled for 5 minutes
>>> INIT: no more processes left in this runlevel
>>>
>>> and then console got  stuck.
>>
>>
>>> What do you have SERIAL_CONSOLE set to in your configuration?
>>
>>
>> I have set SERIAL_CONSOLE="115200 ttyAMA2". As we are using ttyAMA2 for
>> console.
>
>
> What is your target device?  Do you really have /dev/ttyAMA2 serial port??
>
>

 I am building rootfs/uImage with default toolchain used in yocto.
 Is it problem of toolchain?.
 Should I build with our toolchain( we use CodeSourcery)?.
>>>
>>>
>>> Nothing above suggests a toolchain problem. You have an error running
>>> the postinst scripts from the various rpm packages. Some instrumentation
>>> in those scripts (and the parent script) would help narrow down where it
>>> is failing.
>>>
>>> --
>>> Darren
>>>

 Best Regards,
 Om Prakash Pal
 
 From: Bruce Ashfield [bruce.ashfi...@windriver.com]
 Sent: Sunday, May 06, 2012 6:00 PM
 To: Om Prakash PAL
 Cc: Bruce Ashfield; yocto@yoctoproject.org; Richard Purdie
 Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

 On 12-05-06 5:43 AM, Om Prakash PAL wrote:
>
> Hi Bruce,
> I am getting some problem in do_install:
>
> NOTE: Running task 1535 of 1710 (ID: 517,
> /home/apallan/yocto/poky-edison-6.0/meta-u8500/recipes-kernel/linux/linux-u8500.bb,
> do_install)
> NOTE: package
> linux-u8500-3.2+git1+0a81a5eaa7a5c1216cbd087bec5ec7cd8a448383-r10: task
> do_install: Started
>
> and I waited for ~15hr to complete task do_install: but not completed
> and i am not getting any Errors/warnings.
> Is there any problem?.
> I have checked that my vmlinux/uImage/zImage has been created
> successfully but rootfs has not been created till now.
>
> here is my .bb file that is building my local_kernel.
>
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> KMACHINE = "dev"
> YOCTO_KERNEL_EXTERNAL_BRANCH ?= "dev"
>
> KBRANCH = "${KMACHINE}"
> KMETA = "meta"

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

2012-06-21 Thread Mark Hatle

On 6/21/12 10:25 AM, Elvis Dowson wrote:

Hi,
I just updated my yocto repos and tried a fresh build.

There are two errors, see below:

My bblayers.conf file looks like this:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "4"

BBFILES ?= ""
BBLAYERS ?= " \
/tool/yocto/poky/meta \
/tool/yocto/poky/meta-yocto \
/tool/yocto/meta-openembedded/meta-oe \
/tool/yocto/meta-xilinx \
"

And when I run the bitake core-image-minimal;bitbake meta-toolchain I get the
following errors:

$ bitbake core-image-minimal;bitbake meta-toolchain;
Pseudo is not present but is required, building this first before the main build
WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h: file
could not be found | ETA: 00:00:49
WARNING: Unable to get checksum for python-numpy SRC_URI entry numpyconfig.h:
file could not be found
WARNING:
/tool/yocto/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
WARNING: /tool/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it is
recommended to set SYSTEMD_PACKAGES as -systemd
Parsing recipes: 100%
||
Time: 00:00:37
Parsing of 1186 .bb files complete (0 cached, 1186 parsed). 1524 targets, 40
skipped, 0 masked, 0 errors.
WARNING: BBPATH references the current directory, either through an empty
entry, or a '.'.
This is unsafe and means your layer configuration is adding empty
elements to BBPATH.
Please check your layer.conf files and other BBPATH settings to remove
the current working directory references.

The above is a warning, it is a configuration problem with one or more
layer.conf file within a layer. But it's a warning, the build will continue.

ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker
(see sanity.conf).
Following is the list of potential problems / advisories:

PATH contains '.' or '', which will break the build, please remove this.

The above is an error. Your shell environment's "PATH" is broken. You have
either '' (blank) or '.' within your path.

Run the following in your shell: echo "${PATH}"

If you see something like:

/usr/bin:/bin:~/bin:.

It's the '.' that is the problem. Rewrite your path by removing the '.' item..
(similarly if it contains '::' or ends with ':' that is the blank problem)

--Mark

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

PATH contains '.' or '', which will break the build, please remove this.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

Best regards,

Elvis Dowson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

2012-06-21 Thread Jack Mitchell

On 21/06/12 16:41, Mark Hatle wrote:

On 6/21/12 10:25 AM, Elvis Dowson wrote:

Hi,
I just updated my yocto repos and tried a fresh build.

There are two errors, see below:

My bblayers.conf file looks like this:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "4"

BBFILES ?= ""
BBLAYERS ?= " \
/tool/yocto/poky/meta \
/tool/yocto/poky/meta-yocto \
/tool/yocto/meta-openembedded/meta-oe \
/tool/yocto/meta-xilinx \
"

And when I run the bitake core-image-minimal;bitbake meta-toolchain
I get the following errors:

$ bitbake core-image-minimal;bitbake meta-toolchain;
Pseudo is not present but is required, building this first before the
main build
WARNING: Unable to get checksum for python-numpy SRC_URI entry
config.h: file could not be found | ETA: 00:00:49
WARNING: Unable to get checksum for python-numpy SRC_URI entry
numpyconfig.h: file could not be found
WARNING:
/tool/yocto/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
WARNING:
/tool/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
Parsing recipes: 100%
||
Time: 00:00:37
Parsing of 1186 .bb files complete (0 cached, 1186 parsed). 1524
targets, 40 skipped, 0 masked, 0 errors.
WARNING: BBPATH references the current directory, either through an
empty entry, or a '.'.
This is unsafe and means your layer configuration is adding
empty elements to BBPATH.
Please check your layer.conf files and other BBPATH settings to
remove the current working directory references.

The above is a warning, it is a configuration problem with one or more
layer.conf file within a layer. But it's a warning, the build will
continue.

ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable
the checker (see sanity.conf).

Following is the list of potential problems / advisories:

PATH contains '.' or '', which will break the build, please
remove this.

The above is an error. Your shell environment's "PATH" is broken.
You have either '' (blank) or '.' within your path.

Run the following in your shell: echo "${PATH}"

If you see something like:

/usr/bin:/bin:~/bin:.

It's the '.' that is the problem. Rewrite your path by removing the
'.' item.. (similarly if it contains '::' or ends with ':' that is the
blank problem)

--Mark

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Loaded 1523 entries from dependency cache.
Parsing recipes: 100%
||
Time: 00:00:07
Parsing of 1186 .bb files complete (1184 cached, 2 parsed). 1524
targets, 40 skipped, 0 masked, 0 errors.
WARNING: BBPATH references the current directory, either through an
empty entry, or a '.'.
This is unsafe and means your layer configuration is adding
empty elements to BBPATH.
Please check your layer.conf files and other BBPATH settings to
remove the current working directory references.
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable
the checker (see sanity.conf).

Following is the list of potential problems / advisories:

PATH contains '.' or '', which will break the build, please
remove this.

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit
code.

Best regards,

Elvis Dowson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

I also started receiving this error about a week ago, my path is as follows:

[jack@archHP r0005]$ echo "${PATH}"
/home/jack/Projects/poky-denzil.git/scripts:/home/jack/Projects/poky-denzil.git/bitbake/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/core_perl

However (from what I can see) this doesn't feature the issue mentioned?

Regards,

Jack Mitchell (j...@embed.me.uk)
Embedded Syst

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

2012-06-21 Thread Khem Raj

On Thu, Jun 21, 2012 at 8:25 AM, Elvis Dowson  wrote:
> BBFILES ?= ""
> BBLAYERS ?= " \
>  /tool/yocto/poky/meta \
>  /tool/yocto/poky/meta-yocto \
>  /tool/yocto/meta-openembedded/meta-oe \
>  /tool/yocto/meta-xilinx \
>  "
>
what does

bitbake -e  | grep -e "^BBPATH="

show
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] sanity.bbclass: Print BBPATH when warning of bad components

2012-06-21 Thread Gary Thomas

The new warning/check for illegal BBPATH components is extended
to actually print the list of elements.  This will make it easier
for the user to identify where the error(s) come from.

Signed-off-by: Gary Thomas 
---
 meta/classes/sanity.bbclass |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 6ed1e6f..fe7ece7 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -396,7 +396,7 @@ def check_sanity(sanity_data):
 "layer configuration is adding empty elements to BBPATH.\n\t "\
 "Please check your layer.conf files and other BBPATH "\
 "settings to remove the current working directory "   \
-"references.");
+"references.\n\tBBPATH = ", str(bbpaths));
 
 if sanity_data.getVar('TARGET_ARCH', True) == "arm":
 # This path is no longer user-readable in modern (very recent) Linux
-- 
1.7.7.6

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] master build fail for Cedartrail

2012-06-21 Thread Bodke, Kishore K

Hi,

I get build failure for the master branch for the Cedartrail BSP.

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| ERROR: Function failed: do_configure (see 
/usr/local/src/master-chrome/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.6978
 for further information)
| rpm2cpio.real: signature.c:860: verifyDSA: Assertion `sigp->pubkey_algo == 
(rpmuint8_t)PGPPUBKEYALGO_DSA' failed.
| cpio: premature end of archive


I don't see this build fail in Denzil branch.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Hob - proper way to select machine and customer layers

2012-06-21 Thread jfabernathy


On 06/21/2012 10:49 AM, jfabernathy wrote:
So I thought I'd give hob a test. Basically, I wanted to do what I 
could already do with the command line.


Normally, after I set the environment variables, I edit the local.conf 
to change my machine type and parallel processing options. Then I 
point the download directory to a centralized one on my system, and 
add some License statements and some CORE-IMAGE-EXTRA-INSTALL 
statements for extra packages. Then I edit the bblayer.conf to had the 
path to my layer and the meta-intel layers.


To use Hob, I set my environment variable and the just ran hob.  It 
was very slow going through the first 63 packages. I think this is 
because parallel options had not been set and the packages were all 
being downloaded again.  But after I got to the UI of hob, I got 
errors adding my layers to get to the meta-intel layers I wanted.  So 
I started over and edited local.conf and bblayer.conf prior to 
launching hob.  Now I could see my machine from meta-intel, but I 
could not add my layer in. Parsing errors.


Before I report an error, I wanted to see if I have the hob startup 
process right. The issues is around the right way to add 
meta-intel/meta-cedartrail and my personal layer in my home directory.


Any advice?

JIm A

My experimenting tells me that currently Hob (denzil) only work with new 
added layers that are in the poky directory and not in your home 
directory.  This is a different requirement than normal command line 
usage of bitbake.


Jim A
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] master build fail for Cedartrail

2012-06-21 Thread Bodke, Kishore K

Hi Mark,

The rpm verions different in master and denzil.
This is causing the rpm2cpio failure in master.

Thanks
Kishore.


From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Bodke, Kishore K
Sent: Thursday, June 21, 2012 10:36 AM
To: yocto@yoctoproject.org
Subject: [yocto] master build fail for Cedartrail

Hi,

I get build failure for the master branch for the Cedartrail BSP.

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| ERROR: Function failed: do_configure (see 
/usr/local/src/master-chrome/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.6978
 for further information)
| rpm2cpio.real: signature.c:860: verifyDSA: Assertion `sigp->pubkey_algo == 
(rpmuint8_t)PGPPUBKEYALGO_DSA' failed.
| cpio: premature end of archive


I don't see this build fail in Denzil branch.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

Hi Khem,

On Jun 21, 2012, at 8:09 PM, Khem Raj wrote:

> On Thu, Jun 21, 2012 at 8:25 AM, Elvis Dowson  wrote:
>> BBFILES ?= ""
>> BBLAYERS ?= " \
>>  /tool/yocto/poky/meta \
>>  /tool/yocto/poky/meta-yocto \
>>  /tool/yocto/meta-openembedded/meta-oe \
>>  /tool/yocto/meta-xilinx \
>>  "
>> 
> what does
> 
> bitbake -e  | grep -e "^BBPATH="
> 
> show

It shows the following:

BBPATH="/tool/yocto/poky/meta-yocto::/tool/yocto/poky/meta:/tool/yocto/meta-openembedded/meta-oe:/tool/yocto/meta-xilinx"

There is an extra colon : , how can I remove it? 

Best regards,

Elvis Dowson

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] python-numpy SRC_URI warnings

Hi,
  What should I do to get rid of the following python-numpy SRC_URI 
warnings:

WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h: file 
could not be found
WARNING: Unable to get checksum for python-numpy SRC_URI entry numpyconfig.h: 
file could not be found

if I look in the meta-openembedded/meta-oe/recipes-devtools/python/python-numpy 
folder, the config.f and numpyconfig.h files have been moved to an architecture 
specific folder (e.g. arm, mipsel). 

However the python-numpy_1.4.1.bb recipe has not been updated to take the 
target CPU architecture specific file locations into account:

SRC_URI = "${SOURCEFORGE_MIRROR}/numpy/numpy-${PV}.tar.gz \
   file://config.h \
   file://numpyconfig.h \
  "

Is there a variable that I can use for the target CPU architecture? I tried the 
following modifications but it didn't work

SRC_URI = "${SOURCEFORGE_MIRROR}/numpy/numpy-${PV}.tar.gz \
   file://${TARGET_CPU}/config.h \
   file://${TARGET_CPU}/numpyconfig.h \
  "

Is the only alternative to do something like this (which works, btw):

SRC_URI = "${SOURCEFORGE_MIRROR}/numpy/numpy-${PV}.tar.gz \
  "
SRC_URI_arm += " \ 
   file://arm/config.h \
   file://arm/numpyconfig.h \
  "
SRC_URI_mipsel += " \  
   file://mipsel/config.h \
   file://mipsel/numpyconfig.h \
  "

Best regards,

Elvis Dowson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

Hi Khem,
   I noticed that my PATH variable had an extra colon :  , once 
I fixed that, bitbake starts to work.

However, I still get the following warnings:

WARNING: BBPATH references the current directory, either through an empty 
entry, or a '.'.
 This is unsafe and means your layer configuration is adding empty 
elements to BBPATH.
 Please check your layer.conf files and other BBPATH settings to remove 
the current working directory references.

How can I fix this?

The output of the following command is empty

$ bitbake -e core-image-minimal | grep -e "^BBPATH="

$

I don't know what to do, to diagnose the problem and get rid of the warning.

Best regards,

Elvis Dowson

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.

2012-06-21 Thread Khem Raj

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/21/2012 8:05 PM, Elvis Dowson wrote:
> Hi Khem,
> 
> On Jun 21, 2012, at 8:09 PM, Khem Raj wrote:
> 
>> On Thu, Jun 21, 2012 at 8:25 AM, Elvis Dowson
>>  wrote:
>>> BBFILES ?= "" BBLAYERS ?= " \ /tool/yocto/poky/meta \ 
>>> /tool/yocto/poky/meta-yocto \ 
>>> /tool/yocto/meta-openembedded/meta-oe \ /tool/yocto/meta-xilinx
>>> \ "
>>> 
>> what does
>> 
>> bitbake -e  | grep -e "^BBPATH="
>> 
>> show
> 
> It shows the following:
> 
> BBPATH="/tool/yocto/poky/meta-yocto::/tool/yocto/poky/meta:/tool/yocto/meta-openembedded/meta-oe:/tool/yocto/meta-xilinx"
>
>  There is an extra colon : , how can I remove it?
> 

BBLAYERS above meta appears before meta-yocto but in BBPATH meta-yocto
appears before meta. I think meta-yocto/conf/layer.conf has

BBPATH := "${LAYERDIR}:${BBPATH}"

change it to

BBPATH .= ":${LAYERDIR}"

and if you want meta-yocto to appear before meta then rearrange
BBLAYERS above to

BBLAYERS ?= " \
 /tool/yocto/poky/meta-yocto \
 /tool/yocto/poky/meta \
 /tool/yocto/meta-openembedded/meta-oe \
 /tool/yocto/meta-xilinx \
 "

but that may not solve the problem too since now you will get

BBPATH=":/tool/yocto/poky/meta-yocto:/tool/yocto/poky/meta:/tool/yocto/meta-openembedded/meta-oe:/tool/yocto/meta-xilinx"

and it will whine about : at the beginning since that will present and
empty BBPATH when it separates them out for sanity checks.

The fix would be to see if you have : at beginning or end of BBPATH
(_after_ it has been populated) and strip it out.

> Best regards,
> 
> Elvis Dowson
> 


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/j874ACgkQuwUzVZGdMxSgUQCfTMT+9+YaJK3cUuCGhGjr6V/J
0TwAnR3rjGAwIDs2Fg1zGYiculK4BfkP
=EkD0
-END PGP SIGNATURE-
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Porting of specific Kernel/Driver into yocto.