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

[Leon Woestenberg]

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 
> 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.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Emily S]

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 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?

Thanks,
Emily

On Tue, Mar 12, 2019 at 6:24 PM Leon Woestenberg 
wrote:

> 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 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, but I don't actually see
> ${bindir} in it anywhere.
> >
> That last part of the sentence might be the actual problem, in case
> you do not have /usr/bin/env (but /bin/env for example).
>
> > Yes that link is the correct recipe!
> >
> Google power.
>
> Regards,
>
> Leon.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Leon Woestenberg]

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 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, but I don't actually see ${bindir} in it 
> anywhere.
>
That last part of the sentence might be the actual problem, in case
you do not have /usr/bin/env (but /bin/env for example).

> Yes that link is the correct recipe!
>
Google power.

Regards,

Leon.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Emily S]

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, but I don't actually see ${bindir} in it
anywhere.

Yes that link is the correct recipe!

Thanks!
Emily


On Tue, Mar 12, 2019 at 5:27 PM Leon Woestenberg 
wrote:

> 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
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Leon Woestenberg]

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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Leon Woestenberg]

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

This seems to bite more users now and then, the question is whether
some packages do not respect ${bindir} correctly for this case.

Here is a similar report going from morty to rocko, mid-2018:
https://www.yoctoproject.org/irc/%23yocto.2018-06-08.log.html#t2018-06-08T13:35:36

Regards,

Leon.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Emily S]

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
'/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/recipe-sysroot-native/usr/bin/dnf
-y -c
/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/rootfs/etc/dnf/dnf.conf
--setopt=reposdir=/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/rootfs/etc/yum.repos.d
--repofrompath=oe-repo,/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/oe-rootfs-repo
--installroot=/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/rootfs
--setopt=logdir=/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/temp
--nogpgcheck install init-clock run-postinsts locale-base-en-us
locale-base-en-gb' returned 1:
Added oe-repo repo from
/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Tue 12 Mar 2019 09:57:18 PM
UTC.
Error:
 Problem: conflicting requests
  - nothing provides /usr/bin/env needed by init-clock-1.0.0-r0.aarch64

ERROR: core-image-gfex-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/gfex_prototype4-poky-linux/core-image-gfex/1.0-r0/temp/log.do_rootfs.16222
ERROR: Task
(/local/d6/easmith5/rocko_bitbake/meta-l1calo/recipes-core/images/core-image-gfex.bb:do_rootfs)
failed with exit code '1'

On Tue, Mar 12, 2019 at 3:02 PM Leon Woestenberg 
wrote:

> 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 do you see without core-utils?
>
> Regards, Leon.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Leon Woestenberg]

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 do you see without core-utils?

Regards, Leon.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Emily S]

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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW11'19

[sjolley.yp.pm]

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
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*   YP 2.7 M2 rc2 was released on May 5, 2019.
*   We believe we now have all the key components for 2.7M3 in
master-next but have not completed a successful test run with this. In
addition to the list last week, this means M3 will include:

*   5.0 kernel
*   qemuarm transition to armv7
*   Busybox full replacement utils

*   Some invalid source revisions tested in master-next have broken the
autobuilder causing build hangs and failures. With travel and other
distractions, nobody is available to dive in and debug this immediately so
it will block M3.
*   We also want to complete the transition to the new QA process and
test this for M3. Aproov is going to send out details of this imminently, we
believe the main code work is complete and its process/documentation that
remains. We will block on this as we want to use the new QA process for M3
and the final 2.7 release.
*   YP 2.5.3 continues to be blocked on autobuilder-helper changes for
the stable branches and the resulttool changes in master to move to the new
QA process.

 

Planned Releases for YP 2.7:

*   YP 2.7 M3 Cutoff is Feb. 25, 2019
*   YP 2.7 M3 Release Target is Mar. 8, 2019
*   YP 2.7 M4 Cutoff is Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*   YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*   YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

 

Tracking Metrics:

*   WDD 2439 (last week 2436) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1523 (last week 1502)
*   Patches in the Pending State: 657 (43%) [last week 658 (44%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [kernel-cache][PATCH] sound: Re-enable ENS1370 support

[Tom Rini]

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 insertion(+), 1 deletion(-)

diff --git a/cfg/sound.cfg b/cfg/sound.cfg
index 51568d4d592d..6167556d9aca 100644
--- a/cfg/sound.cfg
+++ b/cfg/sound.cfg
@@ -30,7 +30,7 @@ CONFIG_SND_OXYGEN=m
 CONFIG_SND_CTXFI=m
 CONFIG_SND_EMU10K1=m
 CONFIG_SND_EMU10K1X=m
-# CONFIG_SND_ENS1370 is not set
+CONFIG_SND_ENS1370=m
 CONFIG_SND_HDSP=m
 CONFIG_SND_HDSPM=m
 CONFIG_SND_ICE1712=m
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] [yocto-doc][PATCH] ref-manual: fix copy-paste style error (`SRC_URI`)

[Scott Rifenbark]

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

On Mon, Mar 11, 2019 at 8:30 AM Filip Jareš  wrote:

> The update fixes a copy-paste-and-forget-to-update-everything error
> in the documentation of the `SRC_URI` entry in the Reference Manual.
> The `maxdate` paragraph just repeated what is there for the
> neighboring `mindate` paragraph which was incorrect.
>
> What is documented (and patched) here is implemented in the
> `should_apply` function in `meta/lib/oe/patch.py`.
>
> Signed-off-by: Filip Jareš 
> ---
>  documentation/ref-manual/ref-variables.xml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/documentation/ref-manual/ref-variables.xml
> b/documentation/ref-manual/ref-variables.xml
> index 3ffa92c..b49fb25 100644
> --- a/documentation/ref-manual/ref-variables.xml
> +++ b/documentation/ref-manual/ref-variables.xml
> @@ -13798,7 +13798,7 @@
>  
>
>  maxdate -
>  Apply the patch only if
> SRCDATE
> -is not later than
> mindate.
> +is not later than
> maxdate.
>  
>
>  minrev -
>  Apply the patch only if
> SRCREV
> --
> 2.7.4
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto