[yocto] /usr/bin/env requires coreutils?

Emily S easmith5555 at gmail.com
Wed Mar 13 12:17:41 PDT 2019

Hi Leon -

Thanks again for your help.

In /usr/bin right now there seems to be mostly coreutils generated things,
but some python as well. I'll have to double check the hard-coded header in
init-clock, didn't realize anything was hard coded.

I have an additional question for perhaps you or anyone on the list:
With this same OS (yocto rocko & our custom layer meta-l1calo:
https://github.com/kratsg/meta-l1calo) I was previously having issues with
devtmpfs not mounting at boot, but after updating to the most recent rocko
commits in openembedded-core and poky, that issue seemed to go away,
however my boot stops after devtmpfs is mounted (before udev can start).
Additionally I'm not given a login and instead directed immediately to a
shell. I don't think I have changed anything to do with udev or devtmpfs,
does anyone have ideas on why that might be happening? I've attached the
entire boot log.


On Tue, Mar 12, 2019 at 7:05 PM Leon Woestenberg <leon at sidebranch.com>

> Hi Emily,
> On Wed, Mar 13, 2019 at 12:50 AM Emily S <easmith5555 at gmail.com> wrote:
> >
> > Ahh okay you meant just literally if there was anything else in it. An
> additional complication of my setup is that our custom board is in Europe,
> so right now there's no one to load the OS for me and boot, but I will
> check as soon as I can.
> >
> You could check the locally generated filesystem image also, you
> typically do not need access to the board to verify this.
> Something like tar tvf or "wic ls" - depending on your image type(s)
> -- see the Yocto docs for WIC inspection, I don't know from heart.
> (But I would travel to Europe Alps and have the trip paid -- much
> better than remote board access).
> > In regards to your second point, do you mean that the init-clock recipe
> might be trying to install the script in a slightly incorrect location? For
> example it's trying to install in /usr/bin/env when my OS is setup to use
> /bin/env instead?
> >
> I mean "env" could be installed to /bin/env, whereas the "shebang" in
> the header is hard-coded to use /usr/bin/env.
> Solution: remove the hard-coding in init-clock.
> With this, you should be able to inspect further.
> Regards,
> Leon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190313/25c2498c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot.log
Type: application/octet-stream
Size: 22910 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20190313/25c2498c/attachment-0001.obj>

More information about the yocto mailing list