[yocto] extra-cmake-modules-native-5.81.0 Package porting on riscv target using meta-qt5-extra layer #yocto

[sateesh m]

Hi Guys,

I am facing compile-time issue (extra-cmake-modules-native-5.81.0 ). Using 
bitbake extra-cmake-modules it's compiled fine. It is dependent on other 
packages. Using bitbake extra-cmake-modules is compiled success. other 
dependent package expecting extra-cmake-modules-native.

build/tmp-glibc/work/x86_64-linux/extra-cmake-modules-native/5.81.0-r0/temp/run.do_compile.21147'
 failed with exit code 1:
build/tmp-glibc/work/x86_64-linux/extra-cmake-modules-native/5.81.0-r0/build/docs/html
 > build-html.log
*FAILED: docs/doc_format_html*
*Could not import extension ecm (exception: cannot import name 'htmlescape')

* How can I fix this issue or build time it is going to docs so how I can 
disable it.  or any patch available gives some suggestions to fix this issue.

Thanks & Regards,
Sateesh

Regards,
Sateesh

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55029): https://lists.yoctoproject.org/g/yocto/message/55029
Mute This Topic: https://lists.yoctoproject.org/mt/86256016/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] building the kernel's usbipd daemon

[chuck kamas via lists.yoctoproject.org]

Thanks for the quick reply. I looked at the perf recipe, and its quite 
involved. Is there a simpler recipie to use as a template? Perhaps one 
of these?


meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb

meta-openembedded/meta-oe/recipes-kernel/spidev-test/spidev-test.bb

meta-openembedded/meta-oe/recipes-kernel/cpupower/cpupower.bb


all three of these appear to be basically the same very simple bb file.


Chuck


On 10/11/21 5:46 PM, Bruce Ashfield wrote:

On Mon, Oct 11, 2021 at 6:16 PM chuck kamas via lists.yoctoproject.org
 wrote:

Hi all,


I've googled most of the day, but to no avail. How does one compile and
add to the image the daemon usbipd? Is there a bitbake file already for
this? The code is part of the kernel found in the kernel tree:

KERNEL_SRC_PATH/tools/usb/usbip/src

and is invoked from the KERNEL_SRC_PATH/tools directory by calling

make usb


from:
https://wiki.st.com/stm32mpu/wiki/How_to_build_Linux_kernel_user_space_tools

PC $> cd /tools
PC $> make 


I would think that there is a preexisting recipe.

There isn't one that I've ever heard of, and the layerindex
(http://layers.openembedded.org/) confirms that nothing registered
with it provides that recipe.

So if you need it, you'd have to create a recipe .. and submit it to
somewhere like meta-openembedded if appropriate.

Have a look at the perf recipe for one of the ways we build tools out
of the kernel source. Something similar will work in this case.

Bruce


thanks,

Chuck











-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55027): https://lists.yoctoproject.org/g/yocto/message/55027
Mute This Topic: https://lists.yoctoproject.org/mt/86249103/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Error while installing Python modules using pip3 in yocto zeus #zeus

[poornesh]

Greetings !

I am working on Rockpis Board with Yocto Zeus for development . When I am 
trying to install  Python modules " *backports.zoneinfo"* using pip3 I am 
facing the below error . Kindly requesting any suggestions to resolve.

*Error Log:*
-
Building wheels for collected packages: backports.zoneinfo
Building wheel for backports.zoneinfo (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 
/usr/lib/python3.7/site-packages/pip/_vendor/pep517/in_process/_in_process.py 
build_wheel /tmp/tmpj158xpon
cwd: 
/tmp/pip-install-e1zrr5gk/backports-zoneinfo_fe1585f6e0ef47be9df309ad556bbecf
Complete output (39 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-aarch64-3.7
creating build/lib.linux-aarch64-3.7/backports
copying src/backports/__init__.py -> build/lib.linux-aarch64-3.7/backports
creating build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/_zoneinfo.py -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/_version.py -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/_tzpath.py -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/_common.py -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/__init__.py -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
running egg_info
writing src/backports.zoneinfo.egg-info/PKG-INFO
writing dependency_links to src/backports.zoneinfo.egg-info/dependency_links.txt
writing requirements to src/backports.zoneinfo.egg-info/requires.txt
writing top-level names to src/backports.zoneinfo.egg-info/top_level.txt
reading manifest file 'src/backports.zoneinfo.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.png' under directory 'docs'
warning: no files found matching '*.svg' under directory 'docs'
no previously-included directories found matching 'docs/_build'
no previously-included directories found matching 'docs/_output'
adding license file 'LICENSE'
adding license file 'licenses/LICENSE_APACHE'
writing manifest file 'src/backports.zoneinfo.egg-info/SOURCES.txt'
copying src/backports/zoneinfo/__init__.pyi -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
copying src/backports/zoneinfo/py.typed -> 
build/lib.linux-aarch64-3.7/backports/zoneinfo
running build_ext
building 'backports.zoneinfo._czoneinfo' extension
creating build/temp.linux-aarch64-3.7
creating build/temp.linux-aarch64-3.7/lib
*aarch64-poky-linux-gcc -mcpu=cortex-a35+crc+crypto -fstack-protector-strong 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
-Wno-unused-result -Wsign-compare -DNDEBUG -g -O3 -Wa9*
*lib/zoneinfo_module.c:1:10: fatal error: Python.h: No such file or directory*
*1 | #include "Python.h"*
*|  ^~*
*compilation terminated.*
*error: command 'aarch64-poky-linux-gcc' failed with exit status 1*
**
*ERROR: Failed building wheel for backports.zoneinfo*
Failed to build backports.zoneinfo
ERROR: Could not build wheels for backports.zoneinfo which use PEP 517 and 
cannot be installed directly

--

Thanks in Advance

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55026): https://lists.yoctoproject.org/g/yocto/message/55026
Mute This Topic: https://lists.yoctoproject.org/mt/86254469/21656
Mute #zeus:https://lists.yoctoproject.org/g/yocto/mutehashtag/zeus
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] How to trigger Yocto Linux /etc/profile or shell scripts in /etc/profile.d without shell logging in?

[Federico Pellegrin]

Hi Jupiter,
To centralize, agreed that you are using systemd, one way I could see is
setting the variables in systemd-system.conf using the DefaultEnvironment
directive, see:
https://freedesktop.org/software/systemd/man/systemd-system.conf.html

This states:


DefaultEnvironment=¶


Configures environment variables passed to all executed processes. Takes a
space-separated list of variable assignments. See environ(7)
 for details about
environment variables.

Simple "%"-specifier expansion is supported, see below for a list of
supported specifiers.

Example:

DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"

Sets three variables "VAR1", "VAR2", "VAR3".


This should have you variables management in each. Otherwise as you mention
one can put in each script with either Environment to have them explicitly
enumerated or with EnvironmentFile to read from a file, which may also fit
your centralization hopes (but still require one line per startup script at
least) and could be further sourced by non-systemd components as well if
needed. (https://www.freedesktop.org/software/systemd/man/systemd.exec.html
under Environment section)

HTH,
Federico


Il giorno lun 11 ott 2021 alle ore 11:05 Jupiter  ha
scritto:

> Hi Federico,
>
> Thanks for your response.
>
> > /etc/profile and similar are interactive shell (/bash) concepts, not
> really
> > system startup ones. So indeed: just on a login (be it local, ssh and so
> > on) they are executed.
>
> Understood, here is what I try to figure out. I use several systemd
> services to start my tasks, each task is not just a system process, I
> found it also has a system environment similar in user login from
> /etcprofile, /home/user/.profile, my question is where is a system
> environment file that each systemd service runs from?
>
> I also thought that /etc/profile.d files should be automatically
> invoked for each user login, but a systemd service does not run
> /etc/profile.d files.
>
> > If you want to execute something else without the need for logging it,
> you
> > should look elsewhere, depending on your system manager: if systemd you
> > should create a service and enable it, if sysvinit a init.d script.
>
> Understood, that was what I did originally, I have to run the setup
> system environment in each service ExecStart script, that is why I am
> looking for a global environment setup file to avoid duplication of
> putting my environment scripts in each ExecStart execution file.
>
> Thank you.
>
> Kind regards,
>
> - jupiter
>
> > HTH,
> > Federico
> >
> >
> > Il giorno lun 11 ott 2021 alle ore 06:30 JH  ha
> > scritto:
> >
> >> Hi,
> >>
> >> The Yocto uses /etc/profile for root login, but there is no root
> >> physical login in an embedded device so the /etc/profile is never
> >> called, I added a shell script to /etc/profile.d, it was not called
> >> either. Both /etc/profile and scripts in /etc/profile.d can only be
> >> invoked when I physically log into the debug console, that is
> >> impractical. Appreciate your advice, how do you resolve that kind of
> >> problem?
> >>
> >> Thank you.
> >>
> >> Kind regards,
> >>
> >> - jupiter
> >>
> >> 
> >>
> >>
> >
>
>
> --
> "A man can fail many times, but he isn't a failure until he begins to
> blame somebody else."
> -- John Burroughs
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55025): https://lists.yoctoproject.org/g/yocto/message/55025
Mute This Topic: https://lists.yoctoproject.org/mt/86230049/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] building the kernel's usbipd daemon

[Bruce Ashfield]

On Mon, Oct 11, 2021 at 6:16 PM chuck kamas via lists.yoctoproject.org
 wrote:
>
> Hi all,
>
>
> I've googled most of the day, but to no avail. How does one compile and
> add to the image the daemon usbipd? Is there a bitbake file already for
> this? The code is part of the kernel found in the kernel tree:
>
> KERNEL_SRC_PATH/tools/usb/usbip/src
>
> and is invoked from the KERNEL_SRC_PATH/tools directory by calling
>
> make usb
>
>
> from:
> https://wiki.st.com/stm32mpu/wiki/How_to_build_Linux_kernel_user_space_tools
>
> PC $> cd /tools
> PC $> make 
>
>
> I would think that there is a preexisting recipe.

There isn't one that I've ever heard of, and the layerindex
(http://layers.openembedded.org/) confirms that nothing registered
with it provides that recipe.

So if you need it, you'd have to create a recipe .. and submit it to
somewhere like meta-openembedded if appropriate.

Have a look at the perf recipe for one of the ways we build tools out
of the kernel source. Something similar will work in this case.

Bruce

>
> thanks,
>
> Chuck
>
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55024): https://lists.yoctoproject.org/g/yocto/message/55024
Mute This Topic: https://lists.yoctoproject.org/mt/86249103/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW40!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


richard.pur...@linuxfoundation.org

2


mhalst...@linuxfoundation.org

1


r...@burtonini.com

1


Grand Total

4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55023): https://lists.yoctoproject.org/g/yocto/message/55023
Mute This Topic: https://lists.yoctoproject.org/mt/86250196/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.4

[Stephen Jolley]

All,

Below is the list as of top 50 bug owners as of the end of WW41 of who have
open medium or higher bugs and enhancements against YP 3.4.   There are 13
possible work days left until the final release candidates for YP 3.4 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

34


r...@burtonini.com

30


david.re...@windriver.com

22


randy.macl...@windriver.com

16


trevor.gamb...@windriver.com

14


bruce.ashfi...@gmail.com

11


richard.pur...@linuxfoundation.org

10


timothy.t.orl...@intel.com

9


kai.k...@windriver.com

7


bluelightn...@bluelightning.org

6


mhalst...@linuxfoundation.org

5


kiran.surend...@windriver.com

4


jpewhac...@gmail.com

4


qi.c...@windriver.com

4


hongxu@windriver.com

3


chee.yang@intel.com

3


thomas.per...@bootlin.com

2


akuster...@gmail.com

2


mingli...@windriver.com

2


ms...@mvista.com

2


saul.w...@windriver.com

2


raj.k...@gmail.com

1


tony.tascio...@windriver.com

1


yi.z...@windriver.com

1


sangeeta.j...@intel.com

1


jay.shen.t...@intel.com

1


pokyli...@reliableembeddedsystems.com

1


alexandre.bell...@bootlin.com

1


alejan...@enedino.org

1


yf...@uwaterloo.ca

1


open.sou...@oleksandr-kravchuk.com

1


weave...@gmail.com

1


jae...@xilinx.com

1


fransmeulenbro...@yahoo.com

1


kerg...@gmail.com

1


mickael.laventure+yo...@gmail.com

1


ydir...@free.fr

1


devendra.tew...@gmail.com

1


jeanmarie.lemeta...@gmail.com

1


diego.sue...@arm.com

1


aeh...@gmail.com

1


sakib.sa...@windriver.com

1


matthew...@posteo.net

1


douglas.ro...@taitradio.com

1


paul.gortma...@windriver.com

1


p...@pbarker.dev

1


alex.kana...@gmail.com

1


vinay.m.e...@gmail.com

1


shac...@vdoo.com

1


pgowda@gmail.com

1


mister...@web.de

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55022): https://lists.yoctoproject.org/g/yocto/message/55022
Mute This Topic: https://lists.yoctoproject.org/mt/86250079/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 395
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.4", "3.5, "3.99" and "Future", the more pressing/urgent issues
being in "3.4" and then "3.5".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55021): https://lists.yoctoproject.org/g/yocto/message/55021
Mute This Topic: https://lists.yoctoproject.org/mt/86249913/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] building the kernel's usbipd daemon

[chuck kamas via lists.yoctoproject.org]

Hi all,


I've googled most of the day, but to no avail. How does one compile and 
add to the image the daemon usbipd? Is there a bitbake file already for 
this? The code is part of the kernel found in the kernel tree:


KERNEL_SRC_PATH/tools/usb/usbip/src

and is invoked from the KERNEL_SRC_PATH/tools directory by calling

make usb


from: 
https://wiki.st.com/stm32mpu/wiki/How_to_build_Linux_kernel_user_space_tools


PC $> cd /tools
PC $> make 


I would think that there is a preexisting recipe.

thanks,

Chuck



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55020): https://lists.yoctoproject.org/g/yocto/message/55020
Mute This Topic: https://lists.yoctoproject.org/mt/86249103/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto build error

[Khem Raj]

On Sun, Oct 10, 2021 at 6:45 PM JH  wrote:
>
> Hi,
>
> I have following errors:
>
> No GNU_HASH in the ELF binary
> /build/tmp-glibc/work/cortexa7t2hf-neon-oe-linux-gnueabi/solar/1.0.0-0/packages-split/wifi_signal,
> didn't pass LDFLAGS? [ldflags]
>
> So I add --hash-style=gnu to my Makefile:
>
> LD_FLAGS += --hash-style=gnu
> LDFLAGS = LD_FLAGS
>
> But that does not work:
>
> arm-oe-linux-gnueabi-gcc: error: unrecognized command line option
> '--hash-style=gnu'
>
> What is wrong about the error if the  --hash-style=gnu is not the right fix?
>

So it seems your makefile is not respecting the LDFLAGS coming from
the environment during linking.
perhaps you should fix that in your linking rules. hardcoding hash
style like this is not portable.

> Thank you.
>
> Kind regards.
>
> JH
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55019): https://lists.yoctoproject.org/g/yocto/message/55019
Mute This Topic: https://lists.yoctoproject.org/mt/86227801/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] QA notification for completed autobuilder build (yocto-3.4.rc1)

[Richard Purdie]

A build flagged for QA (yocto-3.4.rc1) was completed on the autobuilder and is 
available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.4.rc1


Build hash information: 

bitbake: c78ebac71ec976fdf27ea24767057882870f5c60
meta-agl: 228ecc1dec390138c44299d1c244acda9ad75ce1
meta-arm: 98193f3b6167e07cbb794e96b80d78ca1779ea4f
meta-aws: 27bca81c4d3f0138fda583f9ea98df6152332333
meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400
meta-intel: 90170cf85fe35b4e8dc00eee50053c0205276b63
meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8
meta-openembedded: f2152d79043601eacb70da1a3ab36f5ac56f3e28
oecore: bb1dea6806f084364b6017db2567f438e805aef0
poky: f6d1126fff213460dc6954a5d5fc168606d76b66



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55018): https://lists.yoctoproject.org/g/yocto/message/55018
Mute This Topic: https://lists.yoctoproject.org/mt/86242823/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH 1/2] zephyr-kernel/2.7.0: add recipe

[Naveen Saini]

https://github.com/zephyrproject-rtos/zephyr/commits/v2.7-branch

Keeping the default PREFERRED_VERSION to 2.6.1 for now.

Signed-off-by: Naveen Saini 
---
 .../zephyr-kernel/zephyr-kernel-src-2.7.0.inc   | 17 +
 1 file changed, 17 insertions(+)
 create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.0.inc

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.0.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.0.inc
new file mode 100644
index 000..e3424d2
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.0.inc
@@ -0,0 +1,17 @@
+SRCREV_FORMAT = "default_cmsis"
+SRCREV_default = "8a97c83040c0257d98c329dde55ae10e68544688"
+SRCREV_cmsis = "b0612c97c1401feeb4160add6462c3627fe90fc7"
+SRCREV_nordic = "a6e5299041f152da5ae0ab17b2e44e088bb96d6d"
+SRCREV_stm32 = "5c8275071ec1cf160bfe8c18bbd9330a7d714dc8"
+SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_openthread = "5d706547ebcb0a85e11412bcd88e80e2af98c74d"
+SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
+SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"
+
+ZEPHYR_BRANCH = "v2.7-branch"
+PV = "2.7.0+git${SRCPV}"
+
+SRC_URI:append = " file://0001-cmake-add-yocto-toolchain.patch \
+
file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
+"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55016): https://lists.yoctoproject.org/g/yocto/message/55016
Mute This Topic: https://lists.yoctoproject.org/mt/86232346/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH 2/2] zephyr-kernel/2.5.0: drop recipe

[Naveen Saini]

As v2.7.0 is being added, drop this version support

Signed-off-by: Naveen Saini 
---
 ...phyr-2.5.0-cmake-add-yocto-toolchain.patch | 63 ---
 .../zephyr-kernel/zephyr-kernel-src-2.5.0.inc | 17 -
 2 files changed, 80 deletions(-)
 delete mode 100644 
recipes-kernel/zephyr-kernel/files/0001-zephyr-2.5.0-cmake-add-yocto-toolchain.patch
 delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc

diff --git 
a/recipes-kernel/zephyr-kernel/files/0001-zephyr-2.5.0-cmake-add-yocto-toolchain.patch
 
b/recipes-kernel/zephyr-kernel/files/0001-zephyr-2.5.0-cmake-add-yocto-toolchain.patch
deleted file mode 100644
index caab16f..000
--- 
a/recipes-kernel/zephyr-kernel/files/0001-zephyr-2.5.0-cmake-add-yocto-toolchain.patch
+++ /dev/null
@@ -1,63 +0,0 @@
-From 511745625637da0effca13c5489a392e15d32271 Mon Sep 17 00:00:00 2001
-From: Naveen Saini 
-Date: Tue, 31 Mar 2020 13:22:17 +0800
-Subject: [PATCH] cmake: add yocto toolchain
-
-Upstream status: inappropriate [OE specific]
-
-Signed-off-by: Naveen Saini 

- cmake/compiler/gcc/target.cmake |  7 ---
- cmake/toolchain/yocto/generic.cmake | 13 +
- cmake/toolchain/yocto/target.cmake  |  1 +
- 3 files changed, 14 insertions(+), 7 deletions(-)
- create mode 100644 cmake/toolchain/yocto/generic.cmake
- create mode 100644 cmake/toolchain/yocto/target.cmake
-
-diff --git a/cmake/compiler/gcc/target.cmake b/cmake/compiler/gcc/target.cmake
-index 401cc28db8..5a026f4559 100644
 a/cmake/compiler/gcc/target.cmake
-+++ b/cmake/compiler/gcc/target.cmake
-@@ -66,13 +66,6 @@ if(NOT no_libgcc)
- OUTPUT_STRIP_TRAILING_WHITESPACE
- )
- 
--  assert_exists(LIBGCC_FILE_NAME)
--
--  get_filename_component(LIBGCC_DIR ${LIBGCC_FILE_NAME} DIRECTORY)
--
--  assert_exists(LIBGCC_DIR)
--
--  LIST(APPEND LIB_INCLUDE_DIR "-L\"${LIBGCC_DIR}\"")
-   LIST(APPEND TOOLCHAIN_LIBS gcc)
- endif()
- 
-diff --git a/cmake/toolchain/yocto/generic.cmake 
b/cmake/toolchain/yocto/generic.cmake
-new file mode 100644
-index 00..45e5777e2a
 /dev/null
-+++ b/cmake/toolchain/yocto/generic.cmake
-@@ -0,0 +1,13 @@
-+set(COMPILER gcc)
-+set(LINKER ld)
-+set(BINTOOLS gnu)
-+
-+set(ZEPHYR_SYSROOT ${ZEPHYR_SYSROOT})
-+set(SYSROOT_DIR ${ZEPHYR_SYSROOT})
-+set(LIBC_LIBRARY_DIR "\"${SYSROOT_DIR}\"/")
-+set(LIBC_INCLUDE_DIR ${SYSROOT_DIR}/include)
-+LIST(APPEND TOOLCHAIN_LIBS gcc)
-+
-+LIST(APPEND LIB_INCLUDE_DIR "-L\"${STAGING_LIBDIR}\"")
-+
-+set(TOOLCHAIN_LIBS gcc)
-diff --git a/cmake/toolchain/yocto/target.cmake 
b/cmake/toolchain/yocto/target.cmake
-new file mode 100644
-index 00..9881313609
 /dev/null
-+++ b/cmake/toolchain/yocto/target.cmake
-@@ -0,0 +1 @@
-+# SPDX-License-Identifier: Apache-2.0
--- 
-2.17.1
-
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
deleted file mode 100644
index be75362..000
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
+++ /dev/null
@@ -1,17 +0,0 @@
-SRCREV_FORMAT = "default_cmsis"
-SRCREV_default = "fe7c2efca800a0cf1bccf23aefe08b3c4beb88bf"
-SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
-SRCREV_nordic = "f3434da6446380fcdd426dbe2866af21d0d549b6"
-SRCREV_stm32 = "cc8731dba4fd9c57d7fe8ea6149828b89c2bd635"
-SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
-SRCREV_openthread = "385e19da1ae15f27872c2543b97276a42f102ead"
-SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
-SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
-SRCREV_mbedtls = "24d84ecff195fb15c889d9046e44e4804d626c67"
-
-ZEPHYR_BRANCH = "main"
-PV = "2.5.0+git${SRCPV}"
-
-SRC_URI:append = " file://0001-zephyr-2.5.0-cmake-add-yocto-toolchain.patch \
-
file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
-"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55017): https://lists.yoctoproject.org/g/yocto/message/55017
Mute This Topic: https://lists.yoctoproject.org/mt/86232347/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] How to trigger Yocto Linux /etc/profile or shell scripts in /etc/profile.d without shell logging in?

[JH]

Hi Federico,

Thanks for your response.

> /etc/profile and similar are interactive shell (/bash) concepts, not really
> system startup ones. So indeed: just on a login (be it local, ssh and so
> on) they are executed.

Understood, here is what I try to figure out. I use several systemd
services to start my tasks, each task is not just a system process, I
found it also has a system environment similar in user login from
/etcprofile, /home/user/.profile, my question is where is a system
environment file that each systemd service runs from?

I also thought that /etc/profile.d files should be automatically
invoked for each user login, but a systemd service does not run
/etc/profile.d files.

> If you want to execute something else without the need for logging it, you
> should look elsewhere, depending on your system manager: if systemd you
> should create a service and enable it, if sysvinit a init.d script.

Understood, that was what I did originally, I have to run the setup
system environment in each service ExecStart script, that is why I am
looking for a global environment setup file to avoid duplication of
putting my environment scripts in each ExecStart execution file.

Thank you.

Kind regards,

- jupiter

> HTH,
> Federico
>
>
> Il giorno lun 11 ott 2021 alle ore 06:30 JH  ha
> scritto:
>
>> Hi,
>>
>> The Yocto uses /etc/profile for root login, but there is no root
>> physical login in an embedded device so the /etc/profile is never
>> called, I added a shell script to /etc/profile.d, it was not called
>> either. Both /etc/profile and scripts in /etc/profile.d can only be
>> invoked when I physically log into the debug console, that is
>> impractical. Appreciate your advice, how do you resolve that kind of
>> problem?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jupiter
>>
>> 
>>
>>
>


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55015): https://lists.yoctoproject.org/g/yocto/message/55015
Mute This Topic: https://lists.yoctoproject.org/mt/86230049/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto build error

[Alexander Kanavin]

You need to show the full command line that produces the error.

Alex

On Mon, 11 Oct 2021 at 03:45, JH  wrote:

> Hi,
>
> I have following errors:
>
> No GNU_HASH in the ELF binary
>
> /build/tmp-glibc/work/cortexa7t2hf-neon-oe-linux-gnueabi/solar/1.0.0-0/packages-split/wifi_signal,
> didn't pass LDFLAGS? [ldflags]
>
> So I add --hash-style=gnu to my Makefile:
>
> LD_FLAGS += --hash-style=gnu
> LDFLAGS = LD_FLAGS
>
> But that does not work:
>
> arm-oe-linux-gnueabi-gcc: error: unrecognized command line option
> '--hash-style=gnu'
>
> What is wrong about the error if the  --hash-style=gnu is not the right
> fix?
>
> Thank you.
>
> Kind regards.
>
> JH
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55014): https://lists.yoctoproject.org/g/yocto/message/55014
Mute This Topic: https://lists.yoctoproject.org/mt/86227801/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-