From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: update-alternatives: symlinks are not created
Date: Fri, 24 Jan 2014 09:38:18 +0800 [thread overview]
Message-ID: <52E1C40A.1020601@windriver.com> (raw)
In-Reply-To: <CADV-EXE1HK6Qrg9ksCxdrEzvGEnBiAPFtoy4B967Jr1axtofTQ@mail.gmail.com>
On 01/24/2014 08:48 AM, Yevhen Kyriukha wrote:
> I've built custom image with busybox included and noticed that
> symlinks for mkdir, ls, rm and other programs are not created.
>
> In do_rootfs log I have the following error messages:
> ...
> update-alternatives: error: alternative path /bin/busybox.suid doesn't exist
> ...
> update-alternatives: error: alternative path /bin/busybox.nosuid doesn't exist
> ...
>
I encountered the same problem.
The above error is because we're using update-alternatives from host.
It seems to be caused by recent changes about
opkg/opkg-utils/update-alternatives.
I used the following steps to work around it.
bitbake opkg-utils-native -cpopulate_sysroot -f
bitbake <your-image> -crootfs -f
//Chen Qi
prev parent reply other threads:[~2014-01-24 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 0:48 update-alternatives: symlinks are not created Yevhen Kyriukha
2014-01-24 1:38 ` ChenQi [this message]
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=52E1C40A.1020601@windriver.com \
--to=qi.chen@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 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.