Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: unable to use bitbake -c populate_sdk core-image-minimal on dora
Date: Fri, 17 Jan 2014 12:55:17 +0800	[thread overview]
Message-ID: <52D8B7B5.9010502@windriver.com> (raw)
In-Reply-To: <CAMgc3zNOyfSfz=jUmO2sCDOOJ8=MRwD+EZyAc3t-C6gzn3Ehnw@mail.gmail.com>


Hi Shane,

Thanks for reporting this, I will try to figure it out.

And Nicolas, I'm very sorry that I missed your email.

// Robert

On 01/15/2014 09:16 PM, Shane Volpe wrote:
> I believe I'm also having the same problem Nicolas has reported in
> this thread, here is my output:
>
> Issue 1:
> update-alternatives: Error: cannot register alternative opkg to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/opkg
> since it is already registered to /usr/bin/opkg
>
>
> Issue 2:
> update-alternatives: Error: cannot register alternative passwd to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/passwd
> since it is already registered to /usr/bin/passwd
> update-alternatives: Error: cannot register alternative chfn to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/chfn
> since it is already registered to /usr/bin/chfn
> update-alternatives: Error: cannot register alternative newgrp to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/newgrp
> since it is already registered to /usr/bin/newgrp
> update-alternatives: Error: cannot register alternative chsh to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/chsh
> since it is already registered to /usr/bin/chsh
> update-alternatives: Error: cannot register alternative groups to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/bin/groups
> since it is already registered to /usr/bin/groups
> update-alternatives: Error: cannot register alternative chpasswd to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/usr/sbin/chpasswd
> since it is already registered to /usr/sbin/chpasswd
> update-alternatives: Error: cannot register alternative login to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/bin/login since
> it is already registered to /bin/login
> update-alternatives: Error: cannot register alternative vipw to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/sbin/vipw since
> it is already registered to /sbin/vipw
> update-alternatives: Error: cannot register alternative vigr to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/sbin/vigr since
> it is already registered to /sbin/vigr
> update-alternatives: Error: cannot register alternative su to
> /usr/local/oecore-i686/sysroots/i686-angstromsdk-linux/bin/su since it
> is already registered to /bin/su
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  reply	other threads:[~2014-01-17  4:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 13:16 unable to use bitbake -c populate_sdk core-image-minimal on dora Shane Volpe
2014-01-17  4:55 ` Robert Yang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-30  7:31 Nicolas Dechesne

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=52D8B7B5.9010502@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox