|
useless-rpaths : How to solve it/Know if it should be solved ?
Hello,
I have been dealing with Yocto for about a month, so I am still a beginner.
I am usign a NXP Sabresd board with an iMX6 processor. I have the recipes from oe, bsp, freescale etc downloaded from
Hello,
I have been dealing with Yocto for about a month, so I am still a beginner.
I am usign a NXP Sabresd board with an iMX6 processor. I have the recipes from oe, bsp, freescale etc downloaded from
|
By
Vitor Crestani Goergen <crestanivitor@...>
·
#50787
·
|
|
Re: [meta-cgl][PATCH] ucarp: fix build error with gcc-10
I don't have a tree with this layer in front of me. I just reviewed your proposed fix by setting the compiler flag, while you demonstrated in the pacemaker patch that the issue is easily solved by
I don't have a tree with this layer in front of me. I just reviewed your proposed fix by setting the compiler flag, while you demonstrated in the pacemaker patch that the issue is easily solved by
|
By
Bas Mevissen
·
#50786
·
|
|
Re: [meta-cgl][PATCH] ucarp: fix build error with gcc-10
Could you please send out one?
Could you please send out one?
|
By
Chen Qi
·
#50785
·
|
|
Re: [meta-cgl][PATCH] ucarp: fix build error with gcc-10
Why are you not patching the source to use "extern" where it is needed, like in pacemaker? How many errors does ucarp give?
Then it might also a patch that upstream will take, solving the issue
Why are you not patching the source to use "extern" where it is needed, like in pacemaker? How many errors does ucarp give?
Then it might also a patch that upstream will take, solving the issue
|
By
Bas Mevissen
·
#50784
·
|
|
[meta-cgl][PATCH] meta-cgl-common: depend on meta-python2 layer
It requires meta-python2 to be there at the moment.
More specifically, the crmsh recipe needs python-setuptools-native.
Signed-off-by: Chen Qi <Qi.Chen@...>
---
It requires meta-python2 to be there at the moment.
More specifically, the crmsh recipe needs python-setuptools-native.
Signed-off-by: Chen Qi <Qi.Chen@...>
---
|
By
Chen Qi
·
#50783
·
|
|
[meta-cgl][PATCH] ucarp: fix build error with gcc-10
gcc-10 uses '-fno-common' by default, causing multiple definition
error. Use '-fcommon' to fix this problem.
Signed-off-by: Chen Qi <Qi.Chen@...>
---
gcc-10 uses '-fno-common' by default, causing multiple definition
error. Use '-fcommon' to fix this problem.
Signed-off-by: Chen Qi <Qi.Chen@...>
---
|
By
Chen Qi
·
#50782
·
|
|
[meta-cgl][PATCH] pacemaker: Fix build with -fno-common
From: Mingli Yu <mingli.yu@...>
Starting with GCC >= 10.x, -fno-common is used as default
instead of -fcommon.
Make the function definiton extern to fix the build failure.
Signed-off-by:
From: Mingli Yu <mingli.yu@...>
Starting with GCC >= 10.x, -fno-common is used as default
instead of -fcommon.
Make the function definiton extern to fix the build failure.
Signed-off-by:
|
By
Chen Qi
·
#50781
·
|
|
Re: bitbake recipe / Network UPS tool
its in the build we are assembling the system the past 2 days actually with the ups / power supply and case for prototype... testing will come in days when i have a functional device built
its in the build we are assembling the system the past 2 days actually with the ups / power supply and case for prototype... testing will come in days when i have a functional device built
|
By
Yocto
·
#50780
·
|
|
[meta-security][master][dunfell][PATCH] gitignore added
After running testimage there are some python left overs at
lib/oeqa/runtime/cases/__pycache__/
Signed-off-by: Adrian Freihofer <adrian.freihofer@...>
---
.gitignore | 7 +++++++
1 file
After running testimage there are some python left overs at
lib/oeqa/runtime/cases/__pycache__/
Signed-off-by: Adrian Freihofer <adrian.freihofer@...>
---
.gitignore | 7 +++++++
1 file
|
By
Adrian Freihofer
·
#50779
·
|
|
Re: bitbake recipe / Network UPS tool
Have you got a chance to test something?
-- Maciej PijanowskiEmbedded Systems EngineerGPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com
Have you got a chance to test something?
-- Maciej PijanowskiEmbedded Systems EngineerGPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com
|
By
Maciej Pijanowski
·
#50778
·
|
|
Re: Yocto recipe for Tailscale
#yocto
#golang
Sure. I'm traveling right now, but I'll look to do this in the next week or two.
Mike Thompson
Sure. I'm traveling right now, but I'll look to do this in the next week or two.
Mike Thompson
|
By
Mike Thompson <mthompson@...>
·
#50777
·
|
|
Re: RDEPENDS problem
Hi Quentin,
It turns out that there was a problem in the build of the libcanfestival.so library that was adding in a reference to ../bin/....
This caused the failure that I asked about
Hi Quentin,
It turns out that there was a problem in the build of the libcanfestival.so library that was adding in a reference to ../bin/....
This caused the failure that I asked about
|
By
Greg Wilson-Lindberg
·
#50776
·
|
|
Re: How to *properly* use SSTATE_DUPWHITELIST?
You are totally misunderstanding what this variable does. It has
nothing to do with images or rootfs. Its also definitely not per
recipe.
sstate has an overall view of any output 'deployed' in
You are totally misunderstanding what this variable does. It has
nothing to do with images or rootfs. Its also definitely not per
recipe.
sstate has an overall view of any output 'deployed' in
|
By
Richard Purdie
·
#50775
·
|
|
Re: How to *properly* use SSTATE_DUPWHITELIST?
Quoting "Robert P. J. Day" <rpjday@...>:
Oh, wait, I think I misunderstood this variable entirely --
it's not a per-recipe variable, is it? Its value represents the
combination over all
Quoting "Robert P. J. Day" <rpjday@...>:
Oh, wait, I think I misunderstood this variable entirely --
it's not a per-recipe variable, is it? Its value represents the
combination over all
|
By
Robert P. J. Day
·
#50774
·
|
|
How to *properly* use SSTATE_DUPWHITELIST?
Never had cause to dig into SSTATE_DUPWHITELIST until now,
so a couple questions. (Side Note: This variable is not listed
in the YP Reference Manual variable glossary -- should it be?)
Ran across
Never had cause to dig into SSTATE_DUPWHITELIST until now,
so a couple questions. (Side Note: This variable is not listed
in the YP Reference Manual variable glossary -- should it be?)
Ran across
|
By
Robert P. J. Day
·
#50773
·
|
|
M+ & H bugs with Milestone Movements WW38
All,
YP M+ or high bugs which moved to a new milestone in WW38 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
High
14027
bitbake cooker processes left
All,
YP M+ or high bugs which moved to a new milestone in WW38 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
High
14027
bitbake cooker processes left
|
By
Stephen Jolley
·
#50772
·
|
|
Enhancements/Bugs closed WW38!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
akuster808@...
1
randy.macleod@...
1
Grand Total
2
Thanks,
Stephen K. Jolley
Yocto
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
akuster808@...
1
randy.macleod@...
1
Grand Total
2
Thanks,
Stephen K. Jolley
Yocto
|
By
Stephen Jolley
·
#50771
·
|
|
Yocto Project Status WW38'20
Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now
Next Team Meetings:
Bug Triage meeting Thursday Sept. 24th at 7:30am PDT (https://zoom.us/j/454367603)
Monthly
Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now
Next Team Meetings:
Bug Triage meeting Thursday Sept. 24th at 7:30am PDT (https://zoom.us/j/454367603)
Monthly
|
By
Stephen Jolley
·
#50770
·
|
|
Current Autobuilder Intermittent bugs by the WW created or closed.
All,
Below are the lists of open and closed medium or higher Autobuilder Intermittent bugs by the WW created or closed'.
Opened
Count
Closed
Count
2019WW47
1
2020WW26
2
2020WW8
1
All,
Below are the lists of open and closed medium or higher Autobuilder Intermittent bugs by the WW created or closed'.
Opened
Count
Closed
Count
2019WW47
1
2020WW26
2
2020WW8
1
|
By
Stephen Jolley
·
#50769
·
|
|
Current high bug count owners for Yocto Project 3.2
All,
Below is the list as of top 48 bug owners as of the end of WW38 of who have open medium or higher bugs and enhancements against YP 3.2. There are 28 possible work days left until the final
All,
Below is the list as of top 48 bug owners as of the end of WW38 of who have open medium or higher bugs and enhancements against YP 3.2. There are 28 possible work days left until the final
|
By
Stephen Jolley
·
#50768
·
|