Hi Emily,
On Wed, Mar 13, 2019 at 12:50 AM Emily S 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
>
Hi Leon -
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.
In regards to your second point, do you mean
Hi Emily,
On Tue, Mar 12, 2019 at 11:53 PM Emily S wrote:
>
> When you ask if there is anything in /usr/bin at all I'm not sure what you
> mean, could you elaborate?
>
On the root filesystem, do you see other executables in the /usr/bin/ directory?
> Ahh so you're saying something in the
Hi Leon -
When you ask if there is anything in /usr/bin at all I'm not sure what you
mean, could you elaborate?
Ahh so you're saying something in the init-clock recipe itself is incorrect
in the way it uses ${bindir}? I did not actually write this recipe so I may
be not understanding it fully,
Hi Emily,
I guess the problem is more in your init-clock recipe, and I am
assuming this one:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/init/init-clock_1.0.0.bb
This probably was always incorrect, but the problem now shows with
newer Yocto releases.
Regards,
Leon
--
Hi Emily,
On Tue, Mar 12, 2019 at 10:58 PM Emily S wrote:
>
> The full error is below, but essentially:
> nothing provides /usr/bin/env needed by init-clock-1.0.0-r0.aarch64
>
Do you have anything in /usr/bin at all?
i.e. https://lists.yoctoproject.org/pipermail/yocto/2011-November/003467.html
Hi Leon -
The full error is below, but essentially:
nothing provides /usr/bin/env needed by init-clock-1.0.0-r0.aarch64
Thanks!
Emily
ERROR: core-image-gfex-1.0-r0 do_rootfs: Could not invoke dnf. Command
Hi Emily,
On Tue, Mar 12, 2019 at 7:45 PM Emily S wrote:
>
> It seems like now you need to depend on coreutils to get /usr/bin/env
> working, why is that? Coreutils is a bit big and takes awhile to compile.
> This wasn't the previous behavior, and I'm wondering why it was changed.
>
What issue
Hi all -
It seems like now you need to depend on coreutils to get /usr/bin/env
working, why is that? Coreutils is a bit big and takes awhile to compile.
This wasn't the previous behavior, and I'm wondering why it was changed.
Thanks!
Emily
--
___
Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019
SWAT Team Rotation:
* SWAT lead is currently: Anuj
* SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
* SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*
Both the qemux86 and qemux86-64 targets RRECOMMEND the ens1370 kernel
module and set QB_AUDIO_OPT to support that as one of the audio cards as
well.
Fixes: daadaf7fd7d5 ("yocto-kernel-cache: [PATCH] Update audio support v2")
Signed-off-by: Tom Rini
---
cfg/sound.cfg | 2 +-
1 file changed, 1
Filip,
Thanks for the catch. I have fixed this in the upcoming 2.7 version of the
YP reference guide. You can see the fix here -
https://yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#var-SRC_URI.
I will back-port to the relevant YP-maintained development branches (thud
and sumo).
Scott
12 matches
Mail list logo