Re: [linux-yocto] [yocto-4.14][PATCH] features/kernel-sample: add kernel sample support
Hi bruce The current poky using 4.14, so I need send to 4.14 as well. Thanks. On 2018年05月30日 11:18, Dengke Du wrote: When we build the kernel sample codes, we need to open the samples related configurations. Signed-off-by: Dengke Du --- features/kernel-sample/kernel-sample.cfg | 11 +++ features/kernel-sample/kernel-sample.scc | 1 + 2 files changed, 12 insertions(+) create mode 100644 features/kernel-sample/kernel-sample.cfg create mode 100644 features/kernel-sample/kernel-sample.scc diff --git a/features/kernel-sample/kernel-sample.cfg b/features/kernel-sample/kernel-sample.cfg new file mode 100644 index 000..c2b589f --- /dev/null +++ b/features/kernel-sample/kernel-sample.cfg @@ -0,0 +1,11 @@ +CONFIG_SAMPLES=y +CONFIG_SAMPLE_TRACE_EVENTS=m +CONFIG_SAMPLE_TRACE_PRINTK=m +CONFIG_SAMPLE_KOBJECT=m +CONFIG_SAMPLE_KPROBES=m +CONFIG_SAMPLE_KRETPROBES=m +CONFIG_SAMPLE_HW_BREAKPOINT=m +CONFIG_SAMPLE_KFIFO=m +CONFIG_SAMPLE_CONFIGFS=m +CONFIG_SAMPLE_CONNECTOR=m +CONFIG_SAMPLE_SECCOMP=m diff --git a/features/kernel-sample/kernel-sample.scc b/features/kernel-sample/kernel-sample.scc new file mode 100644 index 000..7ac5bd4 --- /dev/null +++ b/features/kernel-sample/kernel-sample.scc @@ -0,0 +1 @@ +kconf non-hardware kernel-sample.cfg -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-4.14][PATCH] features/kernel-sample: add kernel sample support
When we build the kernel sample codes, we need to open the samples related configurations. Signed-off-by: Dengke Du --- features/kernel-sample/kernel-sample.cfg | 11 +++ features/kernel-sample/kernel-sample.scc | 1 + 2 files changed, 12 insertions(+) create mode 100644 features/kernel-sample/kernel-sample.cfg create mode 100644 features/kernel-sample/kernel-sample.scc diff --git a/features/kernel-sample/kernel-sample.cfg b/features/kernel-sample/kernel-sample.cfg new file mode 100644 index 000..c2b589f --- /dev/null +++ b/features/kernel-sample/kernel-sample.cfg @@ -0,0 +1,11 @@ +CONFIG_SAMPLES=y +CONFIG_SAMPLE_TRACE_EVENTS=m +CONFIG_SAMPLE_TRACE_PRINTK=m +CONFIG_SAMPLE_KOBJECT=m +CONFIG_SAMPLE_KPROBES=m +CONFIG_SAMPLE_KRETPROBES=m +CONFIG_SAMPLE_HW_BREAKPOINT=m +CONFIG_SAMPLE_KFIFO=m +CONFIG_SAMPLE_CONFIGFS=m +CONFIG_SAMPLE_CONNECTOR=m +CONFIG_SAMPLE_SECCOMP=m diff --git a/features/kernel-sample/kernel-sample.scc b/features/kernel-sample/kernel-sample.scc new file mode 100644 index 000..7ac5bd4 --- /dev/null +++ b/features/kernel-sample/kernel-sample.scc @@ -0,0 +1 @@ +kconf non-hardware kernel-sample.cfg -- 2.7.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] Fwd: image-mklibs.bbclass fails
On Mon, May 28, 2018 at 2:10 AM, Ulf Samuelsson wrote:
> Checked out poky
> git checkout -b rocko origin/rocko
> export MACHINE=beaglebone
> . ./oe-init-build-env
>
> Added to local.conf:
> MKLIBS_OPTIMIZED_IMAGES_append = " core-image-minimal"
>
> Result:
>
> /core-image-minimal/1.0-r0/temp/run.mklibs_optimize_image.13363: line
> 133: i586-poky-linux-readelf: command not found
> ...
> Exception: Cannot find
> lib/home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot/lib/ld-linux.so.2
> WARNING:
> /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/run.mklibs_optimize_image.13363:1
> exit 1 from 'mklibs -v --ldlib ${dynamic_loader} --libdir lib --sysroot
> /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot
> --gcc-options
> "--sysroot=/home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot"
> --root
> /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs
> --target `echo i586-poky-linux- | sed 's/-$//' ` -d
> /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/mklibs/dest
> `cat
> /home/ulf/projects/poky-bb/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/mklibs/executables.list`'
> ...
>
> Looks like image-mklibs.bbclass has not been tested since the move to a
> local sysroot happened.
It seems class should be adding a dependency on
virtual/${TARGET_PREFIX}binutils-cross
if that fixes the problem, please send the patch if not file a bug
since there might be more to it.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: Yocto
I think you can effectively build your own image with QT, it seems to me thats what you are interested in. For that you would be able to create a new recipe which includes the core-image-minimal recipe and then adds the needed QT packages and packagegroups via CORE_IMAGE_EXTRA_INSTALL. On Fri, May 25, 2018 at 6:18 AM, Scott Rifenbark wrote: > Hi Nikhil, > > I am forwarding your email to the Yocto Project email group. Someone there > can better help you with your questions. I take care of the Yocto manual > set. > > Thanks, > Scott Rifenbark > > -- Forwarded message - > From: nikh kkvv > Date: Fri, May 25, 2018, 6:03 AM > Subject: Yocto > To: > > > Hi srifenbark, > > > I am Nikhil working as soft ware engineer in kerala. > > Currently i am working with a project which require yocto based file system. > I am using sama5d36-xplained evaluation kit. > > Based on the information from the following site > http://www.at91.com/linux4sam/bin/view/Linux4SAM/YoctoProject build a file > system which support qt images and tested successfully. > > Is there any way to avoid this demo images from this build and add qt > support for bitbake core-image minimal process. > > > Regards > Nikhil > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem with python ssl binding
Jacob On Tue, May 29, 2018 at 5:29 AM, Jakob Hasse wrote: > Hello, > > I'm trying to run IoT edge on our target. But as I'm to starting it, python > yells at me with an undefined symbol error: > > iotedgectl setup --connection-string > "HostName=test-sht-provisioning.azure-devices.net;DeviceId=concentrator2edge;SharedAccessKey=rc+orZCzMhHkQmgPZ//ORMh2fALweUKWhGropd2aXcg=" > --nopas > Traceback (most recent call last): > File "/usr/bin/iotedgectl", line 7, in > from edgectl import coremain > File "/usr/lib/python2.7/site-packages/edgectl/__init__.py", line 12, in > > from edgectl.cli import EdgeCLI > File "/usr/lib/python2.7/site-packages/edgectl/cli/__init__.py", line 1, > in > from edgectl.cli.edgecli import EdgeCLI > File "/usr/lib/python2.7/site-packages/edgectl/cli/edgecli.py", line 7, in > > from edgectl.config import EdgeConfigInputSources > File "/usr/lib/python2.7/site-packages/edgectl/config/__init__.py", line > 10, in > from edgectl.config.edgeconfig import EdgeHostConfig > File "/usr/lib/python2.7/site-packages/edgectl/config/edgeconfig.py", line > 11, in > from edgectl.config.certconfig import EdgeCertConfig > File "/usr/lib/python2.7/site-packages/edgectl/config/certconfig.py", line > 9, in > from edgectl.utils import EdgeUtils > File "/usr/lib/python2.7/site-packages/edgectl/utils/__init__.py", line 1, > in > from edgectl.utils.certutil import EdgeCertUtil > File "/usr/lib/python2.7/site-packages/edgectl/utils/certutil.py", line 6, > in > from OpenSSL import crypto > File "/usr/lib/python2.7/site-packages/OpenSSL/__init__.py", line 8, in > > from OpenSSL import crypto, SSL > File "/usr/lib/python2.7/site-packages/OpenSSL/crypto.py", line 16, in > > from OpenSSL._util import ( > File "/usr/lib/python2.7/site-packages/OpenSSL/_util.py", line 6, in > > from cryptography.hazmat.bindings.openssl.binding import Binding > File > "/usr/lib/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", > line 13, in > from cryptography.hazmat.bindings._openssl import ffi, lib > ImportError: > /usr/lib/python2.7/site-packages/cryptography/hazmat/bindings/_openssl.so: > undefined symbol: pthread_atfork > > I can't really find much information about how to fix this error, especially > since the pthread_atfork function should always be there in pthreads. > > Does anyone know how to fix this? > I think you need to apply this fix in your workspace http://git.openembedded.org/meta-openembedded/commit/?id=49ecf6f65dddecaec57790de8610dc89666e31e6 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Updated invitation: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT) (yocto@yoctoproject.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:-0700 TZOFFSETTO:-0800 TZNAME:PST DTSTART:19701101T02 RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=America/Los_Angeles:20180605T08 DTEND;TZID=America/Los_Angeles:20180605T083000 RRULE:FREQ=MONTHLY;BYDAY=1TU DTSTAMP:20180529T175832Z ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com UID:62kon3jnin570da8ggvcvs9...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c om ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@intel .com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org CREATED:20180524T181406Z DESCRIPTION:We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: https://www.google.com/url?q=http%3A%2F%2Fwebch at.freenode.net%2F%3Fchannels%3D%23yocto\;sa=D\;usd=2\;usg=AFQj CNEvOHVIkxKIrfXWfUxCcVS5_8kh5w" target="_blank">http://webchat.freenode.net /?channels=#yoctoWiki: https://www.yoctoproject.org/pu blic-virtual-meetings/">https://www.yoctoproject.org/public-virtual-meeting s/Bridge is with Zoom at: https://www.google.com/url?q =https%3A%2F%2Fzoom.us%2Fj%2F990892712\;sa=D\;usd=2\;usg=AFQjCN G2F5sUpm-S-RhkqNhXVBd3m1_3LA" target="_blank">https://zoom.us/j/990892712\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~ :~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n\n View your event at https://www.google.com/calendar/event?action=VIEW=Nj Jrb24zam5pbjU3MGRhOGdndmN2czl1OWMgeW9jdG9AeW9jdG9wcm9qZWN0Lm9yZw=MjUjdG hleW9jdG9wcm9qZWN0QGdtYWlsLmNvbTcwZTEzYmNmOTE2M2Q0ZWI4YWI5ODA2NGZkYjg3ZmQ3Y WZhYThkZDQ=America%2FLos_Angeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~ :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::- LAST-MODIFIED:20180529T175832Z LOCATION:Zoom Meeting: https://zoom.us/j/990892712 SEQUENCE:1 STATUS:CONFIRMED SUMMARY:Yocto Project Technical Team Meeting TRANSP:OPAQUE BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:This is an event reminder TRIGGER:-P0DT0H15M0S END:VALARM END:VEVENT END:VCALENDAR invite.ics Description: application/ics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Updated invitation: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT) (yocto@yoctoproject.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:-0700 TZOFFSETTO:-0800 TZNAME:PST DTSTART:19701101T02 RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=America/Los_Angeles:20180605T08 DTEND;TZID=America/Los_Angeles:20180605T083000 RRULE:FREQ=MONTHLY;BYDAY=1TU DTSTAMP:20180529T175559Z ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com UID:62kon3jnin570da8ggvcvs9...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c om ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@intel .com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org CREATED:20180524T181406Z DESCRIPTION:We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: https://www.google.com/url?q=http%3A%2F%2Fwebch at.freenode.net%2F%3Fchannels%3D%23yocto\;sa=D\;usd=2\;usg=AFQj CNEvOHVIkxKIrfXWfUxCcVS5_8kh5w" target="_blank">http://webchat.freenode.net /?channels=#yoctoWiki: https://www.google.com/url?q=ht tps%3A%2F%2Fwww.yoctoproject.org%2Fmonthly-technical-call%2F\;sa=D\ ;usd=2\;usg=AFQjCNHoSQyjbIyR8svGWh4_dnL5VNbyig" target="_blank">https:/ /www.yoctoproject.org/public-virtual-meetings/Bridge is with Zo om at: https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F99 0892712\;sa=D\;usd=2\;usg=AFQjCNG2F5sUpm-S-RhkqNhXVBd3m1_3LA" t arget="_blank">https://zoom.us/j/990892712\n\n-::~:~::~:~:~:~:~:~:~:~:~ :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do n ot edit this section of the description.\n\nView your event at https://www. google.com/calendar/event?action=VIEW=NjJrb24zam5pbjU3MGRhOGdndmN2czl1O WMgeW9jdG9AeW9jdG9wcm9qZWN0Lm9yZw=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvb TcwZTEzYmNmOTE2M2Q0ZWI4YWI5ODA2NGZkYjg3ZmQ3YWZhYThkZDQ=America%2FLos_An geles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: ~:~:~:~:~:~:~:~:~:~:~:~::~:~::- LAST-MODIFIED:20180529T175559Z LOCATION:Zoom Meeting: https://zoom.us/j/990892712 SEQUENCE:1 STATUS:CONFIRMED SUMMARY:Yocto Project Technical Team Meeting TRANSP:OPAQUE BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:This is an event reminder TRIGGER:-P0DT0H15M0S END:VALARM END:VEVENT END:VCALENDAR invite.ics Description: application/ics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Enabling Macro from .bb file
Hello, I have the source code were the part of the code kept inside the #ifdef SOME_MACRO and what would be the correct place to define SOME_MACRO this macro?note: This define is specific to the recipe. Regrds,Ugesh-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
On Tue, May 29, 2018 at 12:25 PM, Osier-mixon, Jeffrey < jeffrey.osier-mi...@intel.com> wrote: > Here are links for shared google calendars for > > > > Public meetings: https://calendar.google.com/calendar/b/2?cid= > dGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvbQ > > > > Release schedule: https://calendar.google.com/calendar/b/2?cid= > M2EwOTI3Y3RwczUxdThyczJqdjF1bGlnZGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ > > > > I’ll add these links to the web page. Please let me know if you have any > trouble with them. > Works fine for me. Thanks! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
Hi Trevor & all Here are links for shared google calendars for Public meetings: https://calendar.google.com/calendar/b/2?cid=dGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvbQ Release schedule: https://calendar.google.com/calendar/b/2?cid=M2EwOTI3Y3RwczUxdThyczJqdjF1bGlnZGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ I’ll add these links to the web page. Please let me know if you have any trouble with them. I will also add a request to provide a timezone helper Jeffrey “Jefro” Osier-Mixon, Intel Corporation Open Source Community Ecosystem Strategist From: Trevor Woerner [mailto:twoer...@gmail.com] Sent: Tuesday, May 29, 2018 9:07 AM To: Michael Halstead Cc: Osier-mixon, Jeffrey ; Stephano Cetola ; yocto@yoctoproject.org; Jolley, Stephen K Subject: Re: [yocto] [Call to Action] Yocto Project Bug Triage On Tue, May 29, 2018 at 11:52 AM, Michael Halstead mailto:mhalst...@linuxfoundation.org>> wrote: The meeting page is https://www.yoctoproject.org/public-virtual-meetings/ for anyone interested. Would it be possible to get event planners interested in https://www.timeanddate.com/worldclock/fixedform.html ? It makes is so easy for participants to determine when the event will occur in their own timezone. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
On Tue, May 29, 2018 at 11:52 AM, Michael Halstead < mhalst...@linuxfoundation.org> wrote: > The meeting page is https://www.yoctoproject.org/public-virtual-meetings/ > for anyone interested. > Would it be possible to get event planners interested in https://www.timeanddate.com/worldclock/fixedform.html ? It makes is so easy for participants to determine when the event will occur in their own timezone. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
The meeting page is https://www.yoctoproject.org/public-virtual-meetings/ for anyone interested. On Tue, May 29, 2018 at 8:39 AM, Osier-mixon, Jeffrey < jeffrey.osier-mi...@intel.com> wrote: > Stephen and I put together a meetings page. I'll work with him on a > shareable calendar this week. > > > Original message > From: Michael Halstead > Date: 5/29/18 8:37 AM (GMT-08:00) > To: Stephano Cetola , Trevor Woerner < > twoer...@gmail.com> > Cc: yocto@yoctoproject.org, "Jolley, Stephen K" < > stephen.k.jol...@intel.com>, "Osier-mixon, Jeffrey" < > jeffrey.osier-mi...@intel.com> > Subject: Re: [yocto] [Call to Action] Yocto Project Bug Triage > > > > On 05/29/2018 08:16 AM, Stephano Cetola wrote: > > On 5/29/18 8:00 AM, Trevor Woerner wrote: > >> Is someone working on putting together a (google?) calendar of the > >> various project (OE Yocto) meetings? > > Great question. > > > > Michael, do we have access to a Yocto Project google account? > > > > --S > > > I don't but I think this is being worked on currently. It appears new > meetings are being scheduled by theyoctoproj...@gmail.com. Whoever > controls that account should be able to make the calendar public. > > -- > Michael Halstead > Linux Foundation / SysAdmin > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] interacting with patchwork / unmerged development work
Hello, One of the minor inconveniences with submitting patches to this project, is to work on a patch against master (for example), submit it, then find that yesterday someone submitted a patch against the same file you're editing causing your patch to not apply with what the maintainer is going to test. Do people have tricks or workflows for syncing their repositories with, say, master PLUS any patches which have been sent to the list since the last time (in this case) master was updated? OR: is there an easy way to retrieve what is going to be tested in the next test cycle? OR: would it be possible to tweak patchwork such that all received patches could be automatically applied to a given branch? Developers could then work off that branch and have a better chance of being in-sync? Maintainers could then prune that branch, removing any patches that have been rejected or need more work. I dug around and found two command-line utilities for interacting with patchwork: - pwclient - git-pw I can't seem to get either to work. Using the following ~/.pwclientrc (which is obtained from the OE patchwork server itself: https://patchwork.openembedded.org/project/oe/ and https://patchwork.openembedded.org/project/oe/pwclientrc/) [options] default=oe [oe] url= https://patchwork.openembedded.org/xmlrpc/ I get a timeout error: $ pwclient list Traceback (most recent call last): File "/home/trevor/local/bin/pwclient", line 10, in sys.exit(main()) File "/home/trevor/local/lib/python2.7/site-packages/pwclient/shell.py", line 190, in main action_list(rpc, filt, submitter_str, delegate_str, format_str) File "/home/trevor/local/lib/python2.7/site-packages/pwclient/patches.py", line 114, in action_list patches = rpc.patch_list(filter.d) File "/usr/lib64/python2.7/xmlrpclib.py", line 1243, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1602, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1283, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1331, in single_request response.msg, xmlrpclib.ProtocolError: For git-pw, it always seems to want a username/password, regardless of the operation, even though listing or retrieving patches shouldn't need a login: $ git config pw.server https://patchwork.openembedded.org $ git config pw.project oe $ git pw patch list Authentication information missing You must configure authentication via git-config or via --token or --username, --password In any case, even if one of these were working, I'd still need to be able to generate a list of patch IDs since the last test. I have no idea how I'd go about doing that since I don't think the last accepted patch ID is known. Also, a list of currently-accepted patches isn't given anywhere either (that I'm aware). Any thoughts? Best regards, Trevor -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
Stephen and I put together a meetings page. I'll work with him on a shareable calendar this week. Original message From: Michael Halstead Date: 5/29/18 8:37 AM (GMT-08:00) To: Stephano Cetola , Trevor Woerner Cc: yocto@yoctoproject.org, "Jolley, Stephen K" , "Osier-mixon, Jeffrey" Subject: Re: [yocto] [Call to Action] Yocto Project Bug Triage On 05/29/2018 08:16 AM, Stephano Cetola wrote: > On 5/29/18 8:00 AM, Trevor Woerner wrote: >> Is someone working on putting together a (google?) calendar of the >> various project (OE Yocto) meetings? > Great question. > > Michael, do we have access to a Yocto Project google account? > > --S > I don't but I think this is being worked on currently. It appears new meetings are being scheduled by theyoctoproj...@gmail.com. Whoever controls that account should be able to make the calendar public. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
On 05/29/2018 08:16 AM, Stephano Cetola wrote: > On 5/29/18 8:00 AM, Trevor Woerner wrote: >> Is someone working on putting together a (google?) calendar of the >> various project (OE Yocto) meetings? > Great question. > > Michael, do we have access to a Yocto Project google account? > > --S > I don't but I think this is being worked on currently. It appears new meetings are being scheduled by theyoctoproj...@gmail.com. Whoever controls that account should be able to make the calendar public. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
On 5/29/18 8:00 AM, Trevor Woerner wrote: > Is someone working on putting together a (google?) calendar of the > various project (OE Yocto) meetings? Great question. Michael, do we have access to a Yocto Project google account? --S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Call to Action] Yocto Project Bug Triage
Is someone working on putting together a (google?) calendar of the various project (OE Yocto) meetings? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW22’18
Current Dev Position: YP 2.6 M1 is accepting patches. Next Deadline: YP 2.6 M1 release is June 11, 2018 SWAT Team Rotation: · SWAT lead is currently: Paul · SWAT team rotation: Paul -> Tracy on June 1, 2018 · SWAT team rotation: Tracy -> Amanda on June 8, 2018 · https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: · 2.4.3 is in QA · 2.3.4 and 2.2.4 are also both queued ready for QA after 2.4.3. · Khem has been doing great work in heading off gcc 8.x issues and several patches have merged in this area · We continue to struggle to get green builds for patch merging, there are a lot of patches being posted and we’re doing the best we can to get these tested, the good ones merged and feedback given on the problematic ones. · We could do with getting a feel for who is using/interested in mips/powerpc support and which areas of those architectures they may be using. We could do with rationalizing the test matrix and those are some of the slowest emulated platforms we have, there are also questions about how long support will be maintained in glibc/gcc. Planned Releases for YP 2.6: · YP 2.6 M1 Build Target is June 11, 2018 · YP 2.6 M1 Release Target is June 22, 2018 · YP 2.6 M2 Build Target is July 16, 2018 · YP 2.6 M2 Release Target is July 27, 2018 · YP 2.6 M3 Build Target is Aug. 27, 2018 · YP 2.6 M3 Release Target is Sept. 7, 2018 · YP 2.6 M4 Build Target is Oct. 1, 2018 · YP 2.6 M4 Release Target is Oct. 26, 2018 Planned upcoming dot releases: · YP 2.4.3 (Rocko) rc2 is built and in QA see https://wiki.yoctoproject.org/wiki/2.4_QA_Status it is 62% complete. · YP 2.3.4 (Pyro) rc1 is built and in QA see https://wiki.yoctoproject.org/wiki/2.3_QA_Status it is at 7% complete. · YP 2.2.4 (Morty) rc1 is built and in QA see https://wiki.yoctoproject.org/wiki/2.2_QA_Status it hasn’t started yet. Tracking Metrics: · WDD 2508 (last week 2510) (https://wiki.yoctoproject.org/charts/combo.html) · Patches oTotal patches found: 1601 (last week 1599) oPercentage of patches in the Pending State: 47% (last week 47%) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.6_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 INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 •Cell:(208) 244-4460 • Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [4.12] [PATCH 1/2] debugobjects: Make kmemleak ignore debug objects
merged. Bruce On 05/29/2018 01:07 AM, quanyang.w...@windriver.com wrote: From: Waiman Long commit caba4cbbd27d755572730801ac34fe063fc40a32 upstream The allocated debug objects are either on the free list or in the hashed bucket lists. So they won't get lost. However if both debug objects and kmemleak are enabled and kmemleak scanning is done while some of the debug objects are transitioning from one list to the others, false negative reporting of memory leaks may happen for those objects. For example, [38687.275678] kmemleak: 12 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0x92e98aabeb68 (size 40): comm "ksmtuned", pid 4344, jiffies 4298403600 (age 906.430s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 d0 bc db 92 e9 92 ff ff 01 00 00 00 00 00 00 00 38 36 8a 61 e9 92 ff ff 86.a backtrace: [] kmemleak_alloc+0x4a/0xa0 [] kmem_cache_alloc+0xe9/0x320 [] __debug_object_init+0x3e6/0x400 [] debug_object_activate+0x131/0x210 [] __call_rcu+0x3f/0x400 [] call_rcu_sched+0x1d/0x20 [] put_object+0x2c/0x40 [] __delete_object+0x3c/0x50 [] delete_object_full+0x1d/0x20 [] kmemleak_free+0x32/0x80 [] kmem_cache_free+0x77/0x350 [] unlink_anon_vmas+0x82/0x1e0 [] free_pgtables+0xa1/0x110 [] exit_mmap+0xc1/0x170 [] mmput+0x80/0x150 [] do_exit+0x2a9/0xd20 The references in the debug objects may also hide a real memory leak. As there is no point in having kmemleak to track debug object allocations, kmemleak checking is now disabled for debug objects. Signed-off-by: Waiman Long Signed-off-by: Thomas Gleixner Cc: Andrew Morton Link: http://lkml.kernel.org/r/1502718733-8527-1-git-send-email-long...@redhat.com --- init/main.c| 2 +- lib/debugobjects.c | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/init/main.c b/init/main.c index 25c10c6..298e49f 100644 --- a/init/main.c +++ b/init/main.c @@ -634,8 +634,8 @@ asmlinkage __visible void __init start_kernel(void) } #endif page_ext_init(); - debug_objects_mem_init(); kmemleak_init(); + debug_objects_mem_init(); setup_per_cpu_pageset(); numa_policy_init(); if (late_time_init) diff --git a/lib/debugobjects.c b/lib/debugobjects.c index 17afb04..2f5349c 100644 --- a/lib/debugobjects.c +++ b/lib/debugobjects.c @@ -18,6 +18,7 @@ #include #include #include +#include #define ODEBUG_HASH_BITS 14 #define ODEBUG_HASH_SIZE (1 << ODEBUG_HASH_BITS) @@ -110,6 +111,7 @@ static void fill_pool(void) if (!new) return; + kmemleak_ignore(new); raw_spin_lock_irqsave(_lock, flags); hlist_add_head(>node, _pool); debug_objects_allocated++; @@ -1080,6 +1082,7 @@ static int __init debug_objects_replace_static_objects(void) obj = kmem_cache_zalloc(obj_cache, GFP_KERNEL); if (!obj) goto free; + kmemleak_ignore(obj); hlist_add_head(>node, ); } -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] [Call to Action] Yocto Project Bug Triage
Hi All, Sorry for the cross posting but I want to be sure to hit both the Yocto Project and OpenEmbedded communities with this information. It has been brought to our attention that the weekly bug triage has fallen out of the spotlight and we'd like to get it back into focus. We'd like to encourage anyone who is interested to join us. The invite was sent out to the Yocto Project mailing list: https://lists.yoctoproject.org/pipermail/yocto/2018-May/041308.html We meet once per week to discuss new bugs (bugs with no target milestone) and bugs that might have missed their target milestone. This is a chance for the community to weigh in on features or bugs they care about, as well as to volunteer their time to see that those items are completed on schedule. For those who don't know, we track bugs using bugzilla: https://bugzilla.yoctoproject.org/ To quickly view the bugs that we are triaging during the meeting, you can follow along on the wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage We triage bugs in this order: https://wiki.yoctoproject.org/wiki/Bug_Triage#Bug_Triage_Order Joining this meeting can help keep you up to date with the latest news from the OpenEmbedded and Yocto Project communities. It also helps us better understand and meet the community's needs. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Problem with python ssl binding
Hello, I'm trying to run IoT edge on our target. But as I'm to starting it, python yells at me with an undefined symbol error: iotedgectl setup --connection-string "HostName=test-sht-provisioning.azure-devices.net;DeviceId=concentrator2edge;SharedAccessKey=rc+orZCzMhHkQmgPZ//ORMh2fALweUKWhGropd2aXcg=" --nopas Traceback (most recent call last): File "/usr/bin/iotedgectl", line 7, in from edgectl import coremain File "/usr/lib/python2.7/site-packages/edgectl/__init__.py", line 12, in from edgectl.cli import EdgeCLI File "/usr/lib/python2.7/site-packages/edgectl/cli/__init__.py", line 1, in from edgectl.cli.edgecli import EdgeCLI File "/usr/lib/python2.7/site-packages/edgectl/cli/edgecli.py", line 7, in from edgectl.config import EdgeConfigInputSources File "/usr/lib/python2.7/site-packages/edgectl/config/__init__.py", line 10, in from edgectl.config.edgeconfig import EdgeHostConfig File "/usr/lib/python2.7/site-packages/edgectl/config/edgeconfig.py", line 11, in from edgectl.config.certconfig import EdgeCertConfig File "/usr/lib/python2.7/site-packages/edgectl/config/certconfig.py", line 9, in from edgectl.utils import EdgeUtils File "/usr/lib/python2.7/site-packages/edgectl/utils/__init__.py", line 1, in from edgectl.utils.certutil import EdgeCertUtil File "/usr/lib/python2.7/site-packages/edgectl/utils/certutil.py", line 6, in from OpenSSL import crypto File "/usr/lib/python2.7/site-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import crypto, SSL File "/usr/lib/python2.7/site-packages/OpenSSL/crypto.py", line 16, in from OpenSSL._util import ( File "/usr/lib/python2.7/site-packages/OpenSSL/_util.py", line 6, in from cryptography.hazmat.bindings.openssl.binding import Binding File "/usr/lib/python2.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 13, in from cryptography.hazmat.bindings._openssl import ffi, lib ImportError: /usr/lib/python2.7/site-packages/cryptography/hazmat/bindings/_openssl.so: undefined symbol: pthread_atfork I can't really find much information about how to fix this error, especially since the pthread_atfork function should always be there in pthreads. Does anyone know how to fix this? Thanks and All the Best, Jakob -- Jakob Hasse Software Developement E: jakob.ha...@smart-home-technology.ch T: +41 44 552 02 66 Smart Home Technology GmbH www.smart-home-technology.ch -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] HELP: Release Candidate Build for yocto-2.4.3.rc2 now available.
Hi David, On Tue, 2018-05-29 at 03:36 +, Reyna, David wrote: > I apologize for sending this patch for Toaster for Roco 2.4.3 very > late. I have been focused on Sumo and I thought I had more time. > > The Toaster for Rocko is broken on HEAD. There are two patches that > made it into master and Sumo, but missed Rocko. > > I have just now sent the missing patch set to "bitbake-dev". The > first patch fixes an error that breaks the initialization of Toaster. > The second patches fixes a change in behavior for Django that creates > an extra thread that blocks Toaster from shutting down. > > Please accept these patches for Rocko. They are confined to Toaster > and do not affect the rest of the release. I've added the patches onto the rocko/2.36 branches but 2.4.3 is already in QA now so we'd have to break process to add those in potentially untested or go to an rc3. At least they will be on the branch ready for update for anyone that runs into the issue and we can release note. Lets see what else (if anything) is found in rc2... Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Debugging race conditions in image creation
> The issue seems to be related to a missing bootloader file (they both depend on the exact same bootloader): images/senic-hub/u-boot-sunxi-with-spl.bin.1 It seems that sometimes the `.1` is added to the file name and all the other actions depend on the `u-boot-sunxi-with-spl.bin`. And that causes the failure. Whenever I examine the variables with `bitbake -e` the "u-boot-sunxi-with-spl.bin.1" is never mentioned always "u-boot-sunxi-with-spl.bin" That's however only for a single image recipe where the issue never occurs. On Tue, May 29, 2018 at 10:22 AM, Alan Martinovic wrote: > Hi, > I'm building multiple images with the same invocation of the bitbake command. > > When building them one by one, everything works ok. > However when they are both executed in the same time, > issues occur during do_image_sdimg. > > The issue seems to be related to a missing bootloader file (they both > depend on the exact same bootloader): > images/senic-hub/u-boot-sunxi-with-spl.bin.1 > > I'm guessing one image is trying to use the file while the other one > is deleting it or something, so probably some dependency related > issues in the recipes. > > My questions is do you have suggestions on how to debug it? > Is there a global ordered list of executed tasks so I could see what > might be happening in parallel or before the issue happens? > > Or can I explicitly set that a recipe shouldn't be parallelised? > > > Be Well, > Alan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Debugging race conditions in image creation
Hi, I'm building multiple images with the same invocation of the bitbake command. When building them one by one, everything works ok. However when they are both executed in the same time, issues occur during do_image_sdimg. The issue seems to be related to a missing bootloader file (they both depend on the exact same bootloader): images/senic-hub/u-boot-sunxi-with-spl.bin.1 I'm guessing one image is trying to use the file while the other one is deleting it or something, so probably some dependency related issues in the recipes. My questions is do you have suggestions on how to debug it? Is there a global ordered list of executed tasks so I could see what might be happening in parallel or before the issue happens? Or can I explicitly set that a recipe shouldn't be parallelised? Be Well, Alan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
