All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Vidal <develone@sbcglobal.net>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] rootfs fails
Date: Sat, 12 Sep 2015 13:12:25 +0000 (UTC)	[thread overview]
Message-ID: <998678350.1550167.1442063545537.JavaMail.yahoo@mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

Hello All,Thanks after doing "bitbake core-image-sato -c cleansstate"followed by  "bitbake core-image-sato" was able to get the image.During the core-image-sato with no IMAGE_INSTALL_append =  I did see a few warnings that I have not seen before (see below).
    WARNING: QA Issue: gstreamer1.0-plugins-bad: configure was passed
    unrecognised options: --with-egl-window-system [unknown-configure-option]
    
    WARNING: QA Issue: /home/vidal/wkg/yocto/RaspberryPi2/poky/build/
    tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/perl/
    5.22.0-r0/packages-split/perl-ptest/usr/lib/perl/ptest/hints/
    epix.sh is owned by uid 1000, which is the same as the user running bitbake.
     This may be due to host contamination [host-user-contaminated]
Another strange happening is python is missing items to do "python setup.py install" on package
    both repo072015 & repo091015 are using python 2.7.9-r1
    -python-distribute-0.6.32 is missing and 2 new RPMs are installed
    +python-pip-7.1.0 is now being using instead of python-pip-1.5.6
    +python-setuptools-18.2 is now being used.Could this be related to rootfs failing at times?Regards,




Edward Vidal Jr. e-mail develone@sbcglobal.net 915-595-1613

[-- Attachment #2: Type: text/html, Size: 2924 bytes --]

             reply	other threads:[~2015-09-12 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12 13:12 Edward Vidal [this message]
2015-09-23 22:27 ` [meta-raspberrypi] rootfs fails Andrei Gherzan
  -- strict thread matches above, loose matches on Subject: below --
2015-09-11 22:50 Edward Vidal
2015-09-12  0:51 ` Trevor Woerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=998678350.1550167.1442063545537.JavaMail.yahoo@mail.yahoo.com \
    --to=develone@sbcglobal.net \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.