Re: [yocto] opkg 0.3.0 or rootfs task

On Mon, Oct 26, 2015 at 12:46 AM, Christopher Larson wrote: > >> I've just posted patches to the opkg-devel list which should fix this. I >> had >> intended to give them a bit more testing before I sent them but a quick >> fix is >> needed. > > > Thanks for your quick work

[yocto] New prelink version

I just wanted to updated people on the prelinker, and send out news of a new release, but first some project announcements. As some of you may be aware, the previous upstream to the Cross Prelinker has effectively been abandoned. This work was being done by Jakub Jelinek at Red Hat. However,

Re: [yocto] Create uncompressed rootfs

You could mount the .ext3 image on a partition using -o loop or find/customize a different solution using IMAGE_TYPES (i.e. when IMAGE_FSTYPES contains "live") http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time

Re: [yocto] opkg 0.3.0 or rootfs task

On Mon, Nov 2, 2015 at 8:25 AM, Nicolas Dechesne < nicolas.deche...@linaro.org> wrote: > On Mon, Oct 26, 2015 at 12:46 AM, Christopher Larson > wrote: > >> >>> I've just posted patches to the opkg-devel list which should fix this. I >>> had >>> intended to give them a bit

Re: [yocto] opkg 0.3.0 or rootfs task

On 11/02/2015 09:31 AM, Christopher Larson wrote: > > On Mon, Nov 2, 2015 at 8:25 AM, Nicolas Dechesne > wrote: > > On Mon, Oct 26, 2015 at 12:46 AM, Christopher Larson >

[yocto] [layerindex-web][PATCH] update.py: fix splitting on _ when getting class inheritance

The code to populate the inherits information was using a function designed to get the recipe name from a file path, but unlike recipe filenames, the underscore isn't treated as special in class filenames and in fact it's quite common to use underscores there; we were ending up with items in the

[yocto] openjpeg on github

Hello All,When a project is using git instead of tar file which branch is used?Is best to be using git or tar file with yocto? Openjepeg is now on github.   The openjpeg 2.1.0 was at SRC_URI = "${SOURCEFORGE_MIRROR}/project/${BPN}.mirror/${PV}/${BPN}-${PV}.tar.gz".   I did the following to

Re: [yocto] should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"?

On 2015-11-02 10:54, Robert P. J. Day wrote: perusing the meta-musl layer, and noticed in layer.conf the line: BB_DANGLINGAPPENDS_WARNONLY ?= "1" i thought this was a bit odd since (at least to me) it seems like the sort of thing a *developer* might set in their local.conf to temporarily

[yocto] populate_sdk and debian packages problem

Hi, I've just moved everything to fido and everything builds fine. One of the reasons for moving to Fido was to use the built toolchain and create an SDK using populate_sdk but it is failing with the following message: ERROR: Unable to install packages. Command

[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Nov. 3, 2015 8:00 AM US Pacific Time

Tuesday, Nov. 3, 2015 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

[yocto] COPY_LIC_DIRS, COPY_LIC_MANIFEST and firmware upgrades

All, I'm on poky/dizzy-1.7.2 and I've been using COPY_LIC_DIRS and COPY_LIC_MANIFEST to include the license text on my image. I noticed something about the way it operates and I'm wondering if it's a problem when it comes to Free and Open Source Software compliance. If I build an image with

Re: [yocto] Create uncompressed rootfs

On Sun, Nov 1, 2015 at 9:20 PM, Roberto wrote: > Hi, > Hi Roberto, > > I apologise if this is not the right channel for asking the following > question. If so, please advise me on a more appropriate support channel. > > > > I am looking for the quickest workflow for

Re: [yocto] Create uncompressed rootfs

* Andre McCurdy [151102 20:35]: > See the "IMAGE_TYPES" variable for a list of rootfs types which are > supported. There's support for creating an uncompressed .tar file, but > I don't see any support for creating a rootfs directory under > tmp/deploy. No, the usual

[yocto] what are the currently-supported beaglebone-flavoured layers?

just checking which layers out there still have value WRT the beaglebone black, and while meta-yocto-bsp and the meta-ti layer clearly(?) are still being updated, the "meta-beagleboard" layer: git://github.com/beagleboard/meta-beagleboard.git listed at layers.openembedded.org apparently

Re: [yocto] should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"?

On Mon, Nov 2, 2015 at 9:54 AM, Robert P. J. Day wrote: > > perusing the meta-musl layer, and noticed in layer.conf the line: > > BB_DANGLINGAPPENDS_WARNONLY ?= "1" should be avoided although meta-musl is a bit core in nature. this is so that it can interface with

Re: [yocto] COPY_LIC_DIRS, COPY_LIC_MANIFEST and firmware upgrades

Martin, > -Original Message- > From: Martin Jansa [mailto:martin.ja...@gmail.com] > Sent: Monday, November 02, 2015 3:32 PM > To: Bryan Evenson > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] COPY_LIC_DIRS, COPY_LIC_MANIFEST and firmware > upgrades > > On

[yocto] Release Candidate Build for yocto-2.0.rc3.rc3 now available.

-e A release candidate build for yocto-2.0.rc3 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc3 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 42cd81d2058e957b0dd223f6017687e134f6c21f meta-fsl-arm :

[yocto] Yocto 1.7.3.rc1 Full Pass test report

Hello, Here is the Full Pass test report for YP 1.7.3.rc1 release. No blockers have been found during the test campaign. The full test report can be accessed here. Test type: Full Pass Release Test Branch: master

[yocto] [PATCH][yocto-autobuilder] buildset-config.controller: Workaround module dependency issue

Dynamically loaded modules are a problem for multilib builds: 32-bit Pango and Gdk-Pixbuf modules in particular do not get included in the image when 32-bit versions of the libraries get included. Proper fix may require extensive changes to dependency handling: Include the required modules