From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: /usr/bin/env dependencies
Date: Wed, 16 Nov 2011 12:39:15 -0600 [thread overview]
Message-ID: <4EC40353.2090906@windriver.com> (raw)
In-Reply-To: <CALs2vteGvK75Kwu8B4sxL+gPyrgN1SwOKTC97Bd=Xh_bdC==Lg@mail.gmail.com>
On 11/15/11 10:19 PM, Mike Tsukerman wrote:
> Hello,
>
> I'm trying to build my own image for my own machine configuration ( based on
> beagleboard )
> and get some errors. Please tell me what package is missing?
>
> error: Failed dependencies:
> | /usr/bin/env is needed by automake-1.11.1-r4.armv7ahf
> | /usr/bin/env is needed by slang-2.2.4-r6.armv7ahf
> | /usr/bin/env is needed by mc-4.7.5.2-r2.armv7ahf
> | /usr/bin/env is needed by autoconf-2.68-r3.armv7ahf
> | /usr/bin/env is needed by intltool-0.40.6-r5.armv7ahf
> | /usr/bin/env is needed by python-core-2.7.2-r0.0.armv7ahf
> | /usr/bin/env is needed by gnu-config-0.1+cvs20080123-r4.armv7ahf
Each of those packages contains a shell script that is invoked with:
#!/usr/bin/env ...
Likely the "..." bit is python.
Usually busybox or coreutils will provide the /usr/bin/env binary.
If your configuration has flattened the directory structure and removed "/usr",
then each of those packages have flaws in them and are not respecting the
revised "bindir" information -- otherwise you are simply missing functionality
in either busybox or coreutils.
--Mark
> --
> Best regards, Mike Tsukerman
>
> jabber: miketsukerman@gmail.com <mailto:miketsukerman@gmail.com>
> jabber: warzon@jabnet.org <mailto:warzon@jabnet.org>
> skype: w_a_r_z_o_n
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2011-11-16 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 4:19 /usr/bin/env dependencies Mike Tsukerman
2011-11-16 18:39 ` Mark Hatle [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=4EC40353.2090906@windriver.com \
--to=mark.hatle@windriver.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.