Hello,
Thank you Fabien Lahoudere for the reply. Well I am running Ubuntu 16 and trying to install yocto for a board. When I run bitbake core-image-x11 I get this error: ERROR: Task 1570 (virtual:native:/~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 106 tasks of which 102 didn't need to be rerun and 2 failed. Waiting for 0 running tasks to finish: Summary: 2 tasks failed: virtual:native:/~/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, do_compile virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, do_compile gmp_5.1.1.bb has this code inside: require gmp.inc LICENSE="LGPLv3&GPLv3" LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \ file://version.c;endline=18;md5=d8c56b52b9092346b9f93b4da65ef790" SRC_URI_append = " file://use-includedir.patch \ file://append_user_provided_flags.patch \ " SRC_URI[md5sum] = "2fa018a7cd193c78494525f236d02dd6" SRC_URI[sha256sum] = "a0d4779f48b36519dfaceb5f987a7c76fcac223258bebea3bb2244310970afad" and when I run the bitbake fsl-image-x11 I also have an error in ncurses.bb require ncurses.inc PR = "${INC_PR}.1" SRC_URI += "file://tic-hang.patch \ file://config.cache \ " SRC_URI[md5sum] = "8cb9c412e5f2d96bc6f459aa8c6282a1" SRC_URI[sha256sum] = "9046298fb440324c9d4135ecea7879ffed8546dd1b58e59430ea07a4633f563b" Best regards and thanks, Theologou Natalia ________________________________ From: yocto-boun...@yoctoproject.org <yocto-boun...@yoctoproject.org> on behalf of yocto-requ...@yoctoproject.org <yocto-requ...@yoctoproject.org> Sent: Thursday, April 6, 2017 6:58 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 79, Issue 23 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: unable to create softlink for precompilied libraries (Khem Raj) 2. Returning non-zero exit code (Natalia Theologou) 3. Re: Returning non-zero exit code (Fabien Lahoudere) 4. Re: Local repo no network help request (Leonardo Sandoval) 5. Re: Local repo no network help request (Fabien Lahoudere) 6. [patchwork][PATCH v4] parsemail.py: Improve find_series_for_mail (Jose Lamego) ---------------------------------------------------------------------- Message: 1 Date: Thu, 6 Apr 2017 06:47:45 -0700 From: Khem Raj <raj.k...@gmail.com> To: chandrasekhar c <chandrasek...@evolute-sys.com> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] unable to create softlink for precompilied libraries Message-ID: <camkf1srgp0i2dqxlqbyjybcbt4ch2-pfl9ej9nnu1vg66mc...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Thu, Apr 6, 2017 at 2:16 AM, chandrasekhar c <chandrasek...@evolute-sys.com> wrote: > Hi, > I have added this FILES_${PN} += " ${libdir}/libMSOComm.so " line in my > recipe still the issue is present > that may not be enough. .so are treated as symlinks and shoved into -dev packages by default. if you need unversioned libraries then you have to let the system know that its not a dev library symlink FILES_${PN} += "${libdir}/*.so" FILES_SOLIBSDEV = "" INSANE_SKIP_${PN} += "dev-so" > Thanks > Chandra > > From: chandrasekhar c <chandrasek...@evolute-sys.com> > Sent: Thu, 6 Apr 2017 14:39:04 GMT+0530 > To: "Fabien Lahoudere " <fabien.lahoud...@collabora.co.uk> > Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> > > Subject: Re: [yocto] unable to create softlink for precompilied libraries > > Hi , > No, I will do the changes and let you know the result. > > Regards, > Chandrasekhar > > From: Fabien Lahoudere <fabien.lahoud...@collabora.co.uk> > Sent: Thu, 6 Apr 2017 14:10:30 GMT+0530 > To: yocto@yoctoproject.org > Subject: Re: [yocto] unable to create softlink for precompilied libraries > > On Thu, 2017-04-06 at 08:08 +0000, chandrasekhar c wrote: >> Hi, >> I have a third party precompilied libraries. I erota a recipe to copy to >> rootfs and create soft >> links for the same. After doing bitbake it didnt throw any errors, but >> when I check th rootfs it >> didn't create any link file. >> Below is my recipe >> >> do_install_append() { >> install -d ${D}${libdir}/ >> install -m 0777 ${S}/libMSO.so.1.2 >> ${D}${libdir}/libMSO.so.1.2 >> ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so >> install -m 0777 ${S}/libMSOComm.so.1.2 >> ${D}${libdir}/libMSOComm.so.1.2 //This is success >> ln -sf libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1 >> //This is success >> ln -sf libMSOComm.so.1 ${D}${libdir}/libMSOComm.so //This >> is not happening >> } >> Can any one tell me a solution for this. > > Did you ship it with FILES_${PN} += " ${libdir}/libMSOComm.so " ? > > >> >> Thanks and Regards, >> Chandrasekhar > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. > ------------------------------ Message: 2 Date: Wed, 5 Apr 2017 15:05:42 +0000 From: Natalia Theologou <natalia_t...@hotmail.com> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: [yocto] Returning non-zero exit code Message-ID: <vi1pr05mb337622d59eab12a6c3d0c045f9...@vi1pr05mb3376.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="iso-8859-1" Hello, While I am trying to bitbake fsl-image-x11 I am having this error: ERROR: Task 1570 (virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 78 tasks of which 74 didn't need to be rerun and 2 failed. Waiting for 0 running tasks to finish: Summary: 2 tasks failed: virtual:native:~/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, do_compile virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, do_compile Does anyone know how to solve it? Thank you in advance, Natalia Theologou -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170405/da453bb9/attachment-0001.html> ------------------------------ Message: 3 of do_compile for both recipe Date: Thu, 06 Apr 2017 16:13:42 +0200 From: Fabien Lahoudere <fabien.lahoud...@collabora.co.uk> To: yocto@yoctoproject.org Subject: Re: [yocto] Returning non-zero exit code Message-ID: <1491488022.25991.55.ca...@collabora.co.uk> Content-Type: text/plain; charset="UTF-8" On Wed, 2017-04-05 at 15:05 +0000, Natalia Theologou wrote: > Hello,? > > While I am trying to bitbake fsl-image-x11 I am having this error: > > ERROR: Task 1570 > (virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, > do_compile) > failed with exit code '1' > NOTE: Tasks Summary: Attempted 78 tasks of which 74 didn't need to be rerun > and 2 failed. > Waiting for 0 running tasks to finish: > > Summary: 2 tasks failed: > ? virtual:native:~/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, > do_compile > ? virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, > do_compile > > Does anyone know how to solve it? Can you give logs of do_compile for both recipe? > > Thank you in advance,? > Natalia Theologou ------------------------------ Message: 4 Date: Thu, 06 Apr 2017 09:30:30 -0500 From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> To: Matthew Phillips <matthew1phill...@gmail.com> Cc: yocto@yoctoproject.org Subject: Re: [yocto] Local repo no network help request Message-ID: <1491489030.31049.11.ca...@linux.intel.com> Content-Type: text/plain; charset="UTF-8" On Wed, 2017-04-05 at 19:57 -0700, Matthew Phillips wrote: > Hi all, > > I am trying to do the following: > > I have a local git repo, pulled manually from a remote repo (via a script). > I have a .bb file set up referencing this repo. This .bb file includes > (among other things): > > >> SRC_URI = "git://${TOPDIR}/../sources/my-repo;protocol=file;branch=master" > >> SRCREV = "${AUTOREV}" > did you get the same result if you hard-coded the pathname? > I do not want to use the network (so BB_NO_NETWORK is 1). > > Although the SRC_URI is pointing to the correct path, the yocto build > fails because it tries to access the network. > > How should I be doing this instead? > > I can run a script (preferably bash atm) before the build if doing > something pre-build will help simplify anything. > > Thank you, > M ------------------------------ Message: 5 Date: Thu, 06 Apr 2017 16:38:29 +0200 From: Fabien Lahoudere <fabien.lahoud...@collabora.co.uk> To: yocto@yoctoproject.org Subject: Re: [yocto] Local repo no network help request Message-ID: <1491489509.25991.58.ca...@collabora.co.uk> Content-Type: text/plain; charset="UTF-8" On Wed, 2017-04-05 at 19:57 -0700, Matthew Phillips wrote: > Hi all, > > I am trying to do the following: > > I have a local git repo, pulled manually from a remote repo (via a script). > I have a .bb file set up referencing this repo. This .bb file includes > (among other things): > > > > SRC_URI = "git://${TOPDIR}/../sources/my-repo;protocol=file;branch=master" > > > SRCREV = "${AUTOREV}" > > I do not want to use the network (so BB_NO_NETWORK is 1). > > Although the SRC_URI is pointing to the correct path, the yocto build > fails because it tries to access the network. > > How should I be doing this instead? Can you use network features with ssh on localhost ? Why don't you create tarball for delivery and cross compile for development? > > I can run a script (preferably bash atm) before the build if doing > something pre-build will help simplify anything. > > Thank you, > M ------------------------------ Message: 6 Date: Thu, 6 Apr 2017 10:58:09 -0500 From: Jose Lamego <jose.a.lam...@linux.intel.com> To: yocto@yoctoproject.org Subject: [yocto] [patchwork][PATCH v4] parsemail.py: Improve find_series_for_mail Message-ID: <1491494289-7439-1-git-send-email-jose.a.lam...@linux.intel.com> Patch Series that are sent as replies to other Series with different patch quantity are not appropriately detected as such, breaking the thread and causing missing revisions. This change improves the find_series_for_mail function to appropriately detect when a message is part of a thread by performing an additional patch-query and detecting cover letters that are replies to cover letters. [YOCTO #10959] Signed-off-by: Jose Lamego <jose.a.lam...@linux.intel.com> --- Notes: Changes in version 4: Only consider messages with Subject starting with "[" as possible cover letters, filtering out reply messages patchwork/bin/parsemail.py | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/patchwork/bin/parsemail.py b/patchwork/bin/parsemail.py index 61c18b2..a68baa2 100755 --- a/patchwork/bin/parsemail.py +++ b/patchwork/bin/parsemail.py @@ -399,9 +399,9 @@ def find_content(project, mail): (x, n) = parse_series_marker(prefixes) refs = build_references_list(mail) is_root = refs == [] - is_cover_letter = is_root and x == 0 patch_prefix = re.match('(\s*\[[^]]*\]\s*)*\[\s*PATCH', mail.get('Subject')) + is_cover_letter = x == 0 and patch_prefix is_patch = patchbuf is not None and patch_prefix drop_patch = not is_attachment and \ @@ -441,7 +441,7 @@ def find_content(project, mail): (ret.series, ret.revision, ret.patch_order, n) = \ find_series_for_mail(project, series_name, msgid, is_patch, - ret.patch_order, n, refs) + ret.patch_order, n, refs, is_cover_letter) ret.revision.n_patches = n or 1 date = mail_date(mail) @@ -535,7 +535,7 @@ def find_patch_order(revisions, previous_patch, order, n_patches): # - we need to create new revisions when the mail is actually a new version # of a previous patch def find_series_for_mail(project, name, msgid, is_patch, order, n_patches, - refs): + refs, is_cover_letter): if refs == []: root_msgid = msgid else: @@ -560,6 +560,20 @@ def find_series_for_mail(project, name, msgid, is_patch, order, n_patches, revision = revision.duplicate(exclude_patches=(order,)) # series has been updated, grab the new instance series = revision.series + else: + try: + prev_patch = SeriesRevisionPatch.objects.get( + revision=revision, order=order).patch + if prev_patch and not prev_patch.msgid == msgid: + # this is a new patch in the thread + revision = revision.duplicate(exclude_patches=(order,)) + series = revision.series + except SeriesRevisionPatch.DoesNotExist: + pass + elif is_cover_letter and not refs == []: + revision = revision.duplicate( + exclude_patches=range(1, revision.n_patches+1),) + series = revision.series except IndexError: if not name: name = SERIES_DEFAULT_NAME -- 2.7.4 ------------------------------ -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. End of yocto Digest, Vol 79, Issue 23 *************************************
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto