Re: [yocto] [PATCH] libsemanage: drop flag: -Wno-unused-but-set-variable

On Apr 30, 2013, at 8:15 PM, Randy MacLeod wrote: > The flag: -Wno-unused-but-set-variable isn't supported on older > versions of gcc such as gcc-4.1.2 which is the native compiler for > RHEL-5.9. Drop this warning flag for both the native and target builds. why drop from target build ? > >

[yocto] [PATCH] libsemanage: drop flag: -Wno-unused-but-set-variable

The flag: -Wno-unused-but-set-variable isn't supported on older versions of gcc such as gcc-4.1.2 which is the native compiler for RHEL-5.9. Drop this warning flag for both the native and target builds. Signed-off-by: Randy MacLeod --- ...semanage-drop-Wno-unused-but-set-variable.patch | 17 ++

[yocto] [PATCH] libselinux: drop flag: -Wno-unused-but-set-variable

The flag: -Wno-unused-but-set-variable isn't supported on older versions of gcc such as gcc-4.1.2 which is the native compiler for RHEL-5.9. I've droped this warning flag for both the native and target builds. Signed-off-by: Randy MacLeod --- .../libselinux-drop-Wno-unused-but-set-variable.patch

Re: [yocto] booting with systemd fails with poky 9.0.0 & meta-ivi 4.0 & meta-intel master

On 04/30/2013 07:12 AM, Felix01 Fischer wrote: Hello, I am not able to boot a genivi-compliant yocto build. The error is "/init:: line XX: mount: not found" I'm using poky 9.0.0, meta-ivi 4.0 & meta-intel master, machine??= crownbay, DISTRO ?= "poky-ivi-systemd" and followed the inherent READM

[yocto] suspending bitbake

I'm quite sure there used to be a time when I could send a SIGTSTP to bitbake (usually by doing a Ctrl-Z) and it along with its children would suspend. This doesn't seem to be the case anymore. Maybe it just so happened that the subprocesses finished quickly after I gave the Ctrl-Z and no new ones

[yocto] [PATCH 8/8] Refactor Latencytop and Perf Handler to remove duplicate code

- both latencytop and perf handler run the same initialization code -> moved the common code to TerminalHandler -> added constants to hold dialog's titles and messages that are different for each handler Signed-off-by: Ioana Grigoropol --- .../sdk/remotetools/actions/IBaseConst

[yocto] [PATCH 7/8] Refactor powertop, oprofile and ust2 models to remote duplicate code

- each of the powertop, oprofile and ust2 commands runs a command remote using RemoteShellExec(former RemoteApplication) following these steps: - start the command - wait to terminate - terminate the command - check exit code - in order to remove duplicate code in t

[yocto] [PATCH 6/8] Refactor RemoteApplication implementation

- remove references that are not used for running remote commands: - remote directory where the command will be ran - remove environment on remote host - rename class to RemoteShellExec since it is a wrapper over a remote shell execution of a command Signed-off-by: Ioana Grigoropo

[yocto] [PATCH 5/8] Remove duplicate code when getting remote data from powertop and ust2

- powertop and ust2 models contain duplicate code that performs the same action when getting data from remote host (method getDataFile) - unify getDataFile method implementation by removing the extra param from ust2-> convert it into a field of BaseModel - move getDataFile

[yocto] [PATCH 3/8] Unify preProcess for all commands models

- all remote tools models(except systemtap) perform the same action in the pre-processing step duplicating the code - move the default code for pre-processing step in the BaseModel - move the local script path and the remote executable location variables that are needed for pre-pr

[yocto] [PATCH 4/8] Add default behaviour for commands for post processing

- after processing the remote tool command, the post processing action is performed - for most of the remote tools commands, this action doesn't actually do something, with to exceptions that perform some file cleanup - provide empty behaviour for post-processing action in BaseModel and

[yocto] [PATCH 2/8] Refactor Model(s) to display customized messages

- each of the remote tools models (systemtap, oprofile, powertop, ust2, ustlegacy) inherits BaseModel class - when running any of these models there are a series of actions performed such as: - init - pre-process - process - post-process - clean - while the

[yocto] [PATCH 1/8] Remove UstLegacyModel since it is no longer supported

- lttng legacy support was dropped but the model remained behind and it should not be maintained anymore Signed-off-by: Ioana Grigoropol --- .../sdk/remotetools/actions/UstModelLegacy.java| 238 1 file changed, 238 deletions(-) delete mode 100644 plugins/org.yocto.sd

[yocto] [PATCH 0/8] Refactoring of remotetools plugin

- refactor all remote tools plugin to have single points of control for remote utilities plugin - remove all duplicate code Ioana Grigoropol (8): Remove UstLegacyModel since it is no longer supported Refactor Model(s) to display customized messages Unify preProcess for all commands models

[yocto] booting with systemd fails with poky 9.0.0 & meta-ivi 4.0 & meta-intel master

Hello, I am not able to boot a genivi-compliant yocto build. The error is "/init:: line XX: mount: not found" I'm using poky 9.0.0, meta-ivi 4.0 & meta-intel master, machine??= crownbay, DISTRO ?= "poky-ivi-systemd" and followed the inherent README. This error occurred with yocto 8.0.1, meta-

Re: [yocto] poky: Bitbake nothing provides error

Thank you Paul 2013/4/29 Paul Eggleton > On Monday 29 April 2013 15:07:27 Katu Txakur wrote: > > The instructions in > > > https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md > > worked > > for me, at least you can get them and have a look at the > > build/conf/local.conf

Re: [yocto] Problem Installing Package Manager in FRI2

Hi, On Sat, 2013-04-06 at 14:24 -0600, Esteban Rivera wrote: > I'm trying to generate an image for the FRI2 using the official Intel > BSP provided in the Yocto Project website, in this image I want to > include at least one package manager. > > I'm Using poky 8.0 with Hob GUI, from the recipes li