[yocto] Mpich and yocto ?

Dear Yocto Member, Does anyone know on how to run poky on mpich cluster ? Thanks, -- * /***/ Sent by Ubuntu LTS 16.04, Kind regards, Riko Ho /***/ * -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] How to build a same package twice with different configurations for same MACHINE?

Hi, Am 18.07.2017 um 15:24 schrieb Ngọc Thi Huỳnh: > [...] > > Both images use busybox package but in different ways. The main-image > can use several busybox' tools but the initial-flasher-image only uses > one or two of them just to complete the flashing goal. > > My question is, is there a

Re: [yocto] Yocto Poky meta browser issue on intel 32 image

On Fri, Jul 21, 2017 at 7:11 AM, Maurizio Galasso wrote: > > Hello, > > > > i'm trying to integrate meta browser recipe for have a chromium instance on > a intel x86 32 bit machine. > > i'm configuring x86 machine and i've integrated the meta-browser proposed by >

Re: [yocto] How do I write a yocto/bitbake recipe to replace the default vsftpd.conf file with my own filE?

On 24.07.2017 07:18, Mohammad Nouri wrote: Hi, I want to replace the default vsftpd.conf file with my own file! My bitbake file looks following: bbexample_1.0.bb DESCRIPTION = "Configuration and extra files for TX28" LICENSE = "CLOSED" LIC_FILES_CHKSUM = "" S =

[yocto] Extra rebuilds when using rm_work

With both pyro and master, I have noticed that when I use 'INHERIT += “rm_work”’ I get extra rebuilds of the image rootfs. My current build uses poky rev 5686f4e1fe5229705b8c7d35895aa03827796d13 Specifically, without “rm_work”: $ . src/poky/oe-init-build-env build-rm-work $ cat >>

[yocto] How do I write a yocto/bitbake recipe to replace the default vsftpd.conf file with my own filE?

Hi, I want to replace the default vsftpd.conf file with my own file! My bitbake file looks following: bbexample_1.0.bb DESCRIPTION = "Configuration and extra files for TX28" LICENSE = "CLOSED" LIC_FILES_CHKSUM = "" S = "${WORKDIR}" SRC_URI += " \ file://ld.so.conf \

[yocto] Yocto Poky meta browser issue on intel 32 image

Hello, i'm trying to integrate meta browser recipe for have a chromium instance on a intel x86 32 bit machine. i'm configuring x86 machine and i've integrated the meta-browser proposed by open-embedded 1. https://codeload.github.com/OSSystems/meta-browser/zip/master 2.

[yocto] information on cedarview support for Yocto Poky

Hello, I am about to work in a cedarview Machine. From what I seeing online it seems that the only available support is for yocto danny. It is the cedarview supported and I’m missing the reference or the system is no longer supported? Can I consider some possible patch on poky? My target is

Re: [yocto] Problems with 'configure' on own recipe [after moving to morty]

> On 25 July 2017 at 16:00 Colin Helliwell > wrote: > > Ah yes, that's true Ross - I should be able to try that approach instead. > However there's obviously been a lot of changes from 1.4 to 1.8 and hence something to be said for a fresh recipe rather

Re: [yocto] Problems with 'configure' on own recipe [after moving to morty]

Ah yes, that's true Ross - I should be able to try that approach instead. > On 25 July 2017 at 15:57 "Burton, Ross" wrote: > > On 25 July 2017 at 15:39, Colin Helliwell > wrote: > > > That is in fact what I blagged as the starting point

Re: [yocto] Problems with 'configure' on own recipe [after moving to morty]

On 25 July 2017 at 15:39, Colin Helliwell wrote: > That is in fact what I blagged as the starting point for 'my' recipe, but > then evolved it so as to use the github head. For my particular [embedded] > platform I also need to switch off some of the configure

Re: [yocto] Problems with 'configure' on own recipe [after moving to morty]

> On 25 July 2017 at 15:20 "Burton, Ross" wrote: > > On 25 July 2017 at 15:08, wrote: > > > This is gonna be a bit of a hard one to describe concisely, but hoping > > someone can advise me on solving it > > I have a recipe of my own

Re: [yocto] Problems with 'configure' on own recipe [after moving to morty]

On 25 July 2017 at 15:08, wrote: > This is gonna be a bit of a hard one to describe concisely, but hoping > someone can advise me on solving it > I have a recipe of my own for an app (NetworkManager) which fetches the > source from its git repo. This recipe

[yocto] Problems with 'configure' on own recipe [after moving to morty]

This is gonna be a bit of a hard one to describe concisely, but hoping someone can advise me on solving it I have a recipe of my own for an app (NetworkManager) which fetches the source from its git repo. This recipe works on krogoth, but is throwing up configure errors on morty. The recipe

Re: [yocto] [Error] Conflict between meta and meta-freescale layer

On Tue, Jul 25, 2017 at 1:29 AM, vr roriz wrote: > Dear all, > > I am trying to compile a core-image-minimal, using the 4.1-2.0 Kernel > version. I am using the meta-freescale layer upon meta and meta-bsp layers. > I keep getting the ERROR: Multiple .bb files are due to be

Re: [linux-yocto] [PATCH 2/3][kernel-cache] common-pc-64: Adds usb-net configs to genericx86-64 builds

No real objections to the series, but it will of course increase the amount of modules/kernel size out of the box. I'm continually balancing the built-in convenience versus the size of the kernel and need to always ask the following question: This sort of thing can be added via KERNEL_FEATURES

Re: [yocto] [meta-virtualization] [recipes-containers] criu version 2.12.1

Hi Frederico, Thanks for the patch, but this needs to go to the meta-virtualization list. Also, we carry a _git recipe in meta-virt to track the various releases (and sometimes points in between). So this patch should be done against that recipe versus creating a new versioned variant.

Re: [yocto] How do I write a yocto/bitbake recipe to replace the default vsftpd.conf file with my own file?

FYI, "recipetool appendfile" can help you create this. See the "recipetool appendfile --help" output for details. Cheers, Paul On Monday, 24 July 2017 11:27:17 AM CEST Burton, Ross wrote: > The package that generates will conflict with the real one. > > Write a bbappend for the recipe you want

[yocto] [meta-virtualization] [recipes-containers] criu version 2.12.1

Hi All, in attach my recipes for Criu 2.12.1. Best regards, Federico Briata --- recipes-containers/criu/criu-2.12.1+gitAUTOINC+14e0bf7baf/0002-criu-Skip-documentation-install.patch | 28 +++

Re: [yocto] Migrating from krogoth to morty (can't boot fitImage)

> On 25 July 2017 at 12:16 Belisko Marek wrote: > > Hi Colin, > > On Tue, Jul 25, 2017 at 12:21 PM, wrote: > > > I'm trying to migrate my krogoth environment to morty. I have custom recipes > > for u-boot and kernel; the only change

Re: [yocto] Migrating from krogoth to morty (can't boot fitImage)

Hi Colin, On Tue, Jul 25, 2017 at 12:21 PM, wrote: > I'm trying to migrate my krogoth environment to morty. I have custom recipes > for u-boot and kernel; the only change necessary to build under morty was to > patch u-boot for gcc6 - other than that the source

[yocto] Migrating from krogoth to morty (can't boot fitImage)

I'm trying to migrate my krogoth environment to morty. I have custom recipes for u-boot and kernel; the only change necessary to build under morty was to patch u-boot for gcc6  - other than that the source versions and configs used are the same. On krogoth I can boot a fitImage kernel, but not on

[yocto] Eclipse Yocto Plugin: Breaks Customize Prespective

Hi, I have noticed that when installing the Yocto Eclipse Plugin in Eclipse Neon (Ubuntu 16.04), I don't have access to the "Customize Prespective" in Eclipse any more. I'm installing from http://downloads.yoctoproject.org/releases/eclipse-plugin/2.3.1/ My plugin setup points to /opt/poky/2.3

[yocto] Perforce fetcher ignores module and label

Hi, I'm upgrading a recipe that fetches the source code from Perforce. The old recipe was: SRC_URI = " \ p4://${P4USER}:${P4PASSWD}:${P4HOST}:${P4PORT}@Depot/path/ perforce/...;module=local/path/relativeto/p4;label=${P4CHANGELIST} \ " With the new version of /lib/bb/fetch2/perforce.py, I

Re: [yocto] SELinux with Busybox on morty

Hi Marco, On similar lines, as Joe suggested please try with refpolicy 2.20151208 from morty, also I would like to recommend start with refpolicy-minimum policy variant, then you can explore other variants like refpolicy-targeted. On Mon, Jul 24, 2017 at 1:15 PM, Marco Ostini

[yocto] [meta-cloud-services][PATCH] spice: set COMPATIBLE_HOST

Set COMPATIBLE_HOST to restrict building only for x86 archs. The configure script clearly requires x86 archs. Message is as below. Only x86 and x86-64 are supported Signed-off-by: Chen Qi --- recipes-support/spice/spice_git.bb | 2 ++ 1 file changed, 2 insertions(+)