From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: error in do_rootfs
Date: Tue, 22 Sep 2015 09:12:40 -0600 [thread overview]
Message-ID: <56016FE8.2070503@mlbassoc.com> (raw)
In-Reply-To: <CAKjpqyLs5AgWkxY2zf_zQ-oWk-j7pqPj6QZRkCFO470rYEa9yQ@mail.gmail.com>
On 2015-09-22 08:53, Mayank Agarwal wrote:
> Thanks Daniel for your help.Please specify how can i remove it
It would be a lot easier to help you diagnose your problem if you provide
more data:
* What version of Yocto are you using?
* What is your target machine?
* What image are you trying to build?
* What changes have you made to local.conf that might affect the result,
e.g. adding any additional packages, etc?
More details, the better.
> On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com <mailto:danielhilst@gmail.com>> wrote:
>
> Will you use bash? If not, try to remove it from image, so /bin/bash isn't created.
>
>
> Cheers,
> - dhs
>
> 2015-09-22 11:42 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com <mailto:mayank77fromindia@gmail.com>>:
>
> From that error:
> Error: not linking /1.0-r0/rootfs//bin/bash to /bin/busybox.nosuid since rootfs//bin/bash exists and is not a link
>
> Any solutions for above,even if i create symlink this error doesn't go
>
> Regards
> Mayank
>
> On Tue, Sep 22, 2015 at 7:47 PM, Daniel. <danielhilst@gmail.com <mailto:danielhilst@gmail.com>> wrote:
>
> There should be a log.do_rootfs in something like BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find a proper failure message with the command
> that triggered the failure and is output.
>
> Cheers,
> - dhs
>
> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com <mailto:mayank77fromindia@gmail.com>>:
>
> Hi,
>
> I am getting the below error in do_rootfs:
>
> ERROR: Unable to install packages. Command
> returned 255:
>
>
> I uderstand this error comes from certificate validation
> failure.
>
> Is there any option i can override the certificate validation
> in do_rootfs and get the binaries imstalled in final image
>
> Regards
> Mayank
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
> /"Do or do not. There is no try"/
> ///*Yoda Master*/
>
>
>
>
>
> --
> /"Do or do not. There is no try"/
> ///*Yoda Master*/
>
>
>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-09-22 15:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 9:36 error in do_rootfs Mayank Agarwal
2015-09-22 14:17 ` Daniel.
2015-09-22 14:42 ` Mayank Agarwal
2015-09-22 14:51 ` Daniel.
2015-09-22 14:53 ` Mayank Agarwal
2015-09-22 15:04 ` Daniel.
2015-09-22 15:07 ` Daniel.
[not found] ` <CAKjpqyK+ZXuE+4jzDfTFO=TLeecGyrL4ab91-eGrLGHJzJADUA@mail.gmail.com>
2015-09-22 16:34 ` Daniel.
2015-09-22 15:12 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-23 12:13 Error " Mayank Agarwal
2015-09-23 12:27 ` Gary Thomas
2015-09-23 6:52 error " 신택현 (Taek Hyun Shin)
2015-09-22 7:08 Mayank Agarwal
2015-09-22 7:12 ` Khem Raj
2015-09-22 7:22 ` Mayank Agarwal
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=56016FE8.2070503@mlbassoc.com \
--to=gary@mlbassoc.com \
--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.