Date   

[PATCH 3/4] Fix bitbake session by disabling sanity checks

Ioana Grigoropol <ioanax.grigoropol@...>
 

- when creating a shell session for Bitbake, we cannot run "bitbake -e -b recipe.bb" just by setting DISABLE_SANITY_CHECKS=1; we must first append DISABLE_SANITY_CHECKS to BB_ENV_EXTRAWHITE

Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@...>
---
.../src/org/yocto/bc/bitbake/BBRecipe.java | 10 +++++-----
.../src/org/yocto/bc/bitbake/ShellSession.java | 16 +++++++++-------
2 files changed, 14 insertions(+), 12 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBRecipe.java b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBRecipe.java
index 7682aee..6a33ade 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBRecipe.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBRecipe.java
@@ -20,24 +20,24 @@ import java.net.URI;
*/
public class BBRecipe extends BBSession {
private final BBSession session;
- private final URI filePath;
+ private final URI fileURI;

public BBRecipe(BBSession session, URI filePath) throws IOException {
super(session.shell, session.pinfo.getURI());
this.session = session;
- this.filePath = filePath;
- this.parsingCmd = "DISABLE_SANITY_CHECKS=1 bitbake -e -b " + filePath;
+ this.fileURI = filePath;
+ this.parsingCmd = "DISABLE_SANITY_CHECKS=\"1\" bitbake -e -b " + filePath.getPath();
}

@Override
public void initialize() throws Exception {
if (this.size() == 0) {
- System.out.println("Failed to parse " + filePath);
+ System.out.println("Failed to parse " + fileURI);
//throw new IOException("Failed to parse " + filePath);
}
}

protected URI getDefaultDepends() {
- return this.filePath;
+ return this.fileURI;
}
}
diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
index a8c46dd..edff746 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
@@ -46,6 +46,7 @@ public class ShellSession {
*/
public static final String TERMINATOR = "#234o987dsfkcqiuwey18837032843259d";
public static final String LT = System.getProperty("line.separator");
+ public static final String exportCmd = "export BB_ENV_EXTRAWHITE=\"DISABLE_SANITY_CHECKS $BB_ENV_EXTRAWHITE\"";

public static String getFilePath(String file) throws IOException {
File f = new File(file);
@@ -69,7 +70,7 @@ public class ShellSession {

private OutputStream pos = null;
//private File initFile = null;
- private String shellPath = null;
+// private String shellPath = null;
private final String initCmd;
private final IHostFile root;
// private final Writer out;
@@ -84,10 +85,10 @@ public class ShellSession {
// } else {
// this.out = out;
// }
- if (shellType == SHELL_TYPE_SH) {
- shellPath = "/bin/sh";
- }
- shellPath = "/bin/bash";
+// if (shellType == SHELL_TYPE_SH) {
+// shellPath = "/bin/sh";
+// }
+// shellPath = "/bin/bash";

initializeShell(new NullProgressMonitor());
}
@@ -95,7 +96,8 @@ public class ShellSession {
private void initializeShell(IProgressMonitor monitor) throws IOException {
try {
IHost connection = RemoteHelper.getRemoteConnectionByName(projectInfo.getConnection().getName());
- RemoteHelper.runCommandRemote(connection, new YoctoCommand("source " + initCmd, root.getAbsolutePath(), ""), monitor);
+ RemoteHelper.runCommandRemote(connection, new YoctoCommand("source " + initCmd, root.getAbsolutePath(), ""), monitor);
+ RemoteHelper.runCommandRemote(connection, new YoctoCommand(exportCmd, root.getAbsolutePath(), ""), monitor);
} catch (Exception e) {
e.printStackTrace();
}
@@ -110,7 +112,7 @@ public class ShellSession {
public String execute(String command, boolean hasErrors) throws IOException {
try {
IHost connection = RemoteHelper.getRemoteConnectionByName(projectInfo.getConnection().getName());
- hasErrors = RemoteHelper.runCommandRemote(connection, new YoctoCommand(command, root.getAbsolutePath(), ""), new NullProgressMonitor());
+ hasErrors = RemoteHelper.runCommandRemote(connection, new YoctoCommand(command, root.getAbsolutePath() + "/build/", ""), new NullProgressMonitor());
return RemoteHelper.getProcessBuffer(connection).getMergedOutputLines();
} catch (Exception e) {
e.printStackTrace();
--
1.7.9.5


[PATCH 2/4] Fix md5sum & sha256sum pattern checks

Ioana Grigoropol <ioanax.grigoropol@...>
 

Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@...>
---
.../ui/wizards/NewBitBakeFileRecipeWizardPage.java | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/NewBitBakeFileRecipeWizardPage.java b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/NewBitBakeFileRecipeWizardPage.java
index eac1211..f1d90c9 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/NewBitBakeFileRecipeWizardPage.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/NewBitBakeFileRecipeWizardPage.java
@@ -96,8 +96,8 @@ public class NewBitBakeFileRecipeWizardPage extends WizardPage {
private static final String CONFIGURE_IN = "configure.in";
private static final String CONFIGURE_AC = "configure.ac";
private static final String AUTOTOOLS = "autotools";
- private static final String md5Pattern = "^[0-9a-e]{32}$";
- protected static final String sha256Pattern = "^[0-9a-e]{64}$";
+ private static final String md5Pattern = "^[0-9a-f]{32}$";
+ protected static final String sha256Pattern = "^[0-9a-f]{64}$";

public NewBitBakeFileRecipeWizardPage(ISelection selection, IHost connection) {
super("wizardPage");
@@ -323,6 +323,7 @@ public class NewBitBakeFileRecipeWizardPage extends WizardPage {

private void handleRemotePopulate(URI srcURI, IProgressMonitor monitor) throws Exception {
RemoteHelper.clearProcessBuffer(connection);
+
populateRecipeName(srcURI);
List<YoctoCommand> commands = new ArrayList<YoctoCommand>();

--
1.7.9.5


[PATCH 1/4] Fix remote deletion of files

Ioana Grigoropol <ioanax.grigoropol@...>
 

- when deleting a file from a remote directory use the URI and not the location of the file which is null

Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@...>
---
.../src/org/yocto/bc/bitbake/BBSession.java | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
index 5f919c3..c5354a4 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
@@ -80,7 +80,7 @@ public class BBSession implements IBBSessionListener, IModelElement, Map {
this.pinfo = new ProjectInfo();
pinfo.setLocation(projectRoot);
pinfo.setInitScriptPath(ProjectInfoHelper.getInitScriptPath(projectRoot));
- this.parsingCmd = "DISABLE_SANITY_CHECKS=1 bitbake -e";
+ this.parsingCmd = "DISABLE_SANITY_CHECKS=\"1\" bitbake -e";
}

public BBSession(ShellSession ssession, URI projectRoot, boolean silent) throws IOException {
@@ -376,7 +376,7 @@ public class BBSession implements IBBSessionListener, IModelElement, Map {
}
try {
if(!initialized) { //recheck
- boolean hasErrors = false;
+ boolean hasErrors = false;
String result = shell.execute(parsingCmd, hasErrors);
if(!hasErrors) {
properties = parseBBEnvironment(result);
@@ -725,7 +725,7 @@ public class BBSession implements IBBSessionListener, IModelElement, Map {
try {
if (initialized && (removed != null || changed != null)) {
for(int i=0;removed != null && i<removed.length;i++) {
- if (this.depends.contains(removed[i].getLocation().toString())) {
+ if (this.depends.contains(removed[i].getLocationURI())) {
initialized = false;
return;
}
--
1.7.9.5


Re: Forcing native binaries to build as 32-bit on a 64-bit host OS?

Paul Eggleton
 

On Tuesday 20 November 2012 14:27:30 Jerrod Peach wrote:
My company has traditionally built all their code on 32-bit systems for
32-bit target architectures. We're now trying to move our build hosts to
64-bit OSes, but that's presenting us with a bit of a problem: some
non-trivial number of native packages don't want to properly build 64-bit
binaries. Rather than fix all those issues right now, we'd like to build
everything as a 32-bit binary on a 64-bit OS. The problem is, I'm not sure
how I'd go about forcing that to happen. Is there some simple mechanism I
can use to force all native packages to build as 32-bit on a 64-bit system?
Sorry for the delay in replying. I've not had to do this myself but I suspect
something like this might do it:

BUILD_ARCH = "i686"

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: IMAGE_INSTALL_append workflow

Eric Bénard <eric@...>
 

Le Tue, 27 Nov 2012 14:00:34 +0000,
Jonas Jonsson L <jonas.l.jonsson@...> a écrit :

I can also confirm this.

A package (I've tried with diffutils & bash) must be built separately before it's added to an image via IMAGE_INSTALL_append.
that seems to work the first time you add something using
IMAGE_INSTALL_append.
Then it fails when you add packages later (bitbake wants to install
the package in the image but doesn't trigger the build of the package
before).

Eric


Re: IMAGE_INSTALL_append workflow

Jonas Jonsson L <jonas.l.jonsson@...>
 

I can also confirm this.

A package (I've tried with diffutils & bash) must be built separately before it's added to an image via IMAGE_INSTALL_append.

/Jonas - fetched poky today

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Trevor Woerner
Sent: den 27 november 2012 03:21
To: Eren Türkay
Cc: yocto@...
Subject: Re: [yocto] IMAGE_INSTALL_append workflow

On Mon, Nov 26, 2012 at 6:52 PM, Trevor Woerner <twoerner@...> wrote:
I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel =
"linux-yocto-rt"" line might be the culprit.
No, it is not related, this problem doesn't need any fancy configuration features. This problem is reproducible with just the plain qemux86 machine and the core-image-minimal image.
Also, before my latest tests I pulled
the latest git repo.

To reproduce this problem:

- use the latest git repositories
- run "source poky/oe-init-build-env qemux86"
- make no modifications to conf/bblayers.conf
- make no changes to conf/local.conf
- run "bitbake core-image-minimal"

After that completes successfully add the following line to your
conf/local.conf:

IMAGE_INSTALL_append = " trace-cmd"

- re-run the build "bitbake core-image-minimal"

This should complete successfully. When it does, modify the last line of conf/local.conf to be:

IMAGE_INSTALL_append = " trace-cmd bash"

- try re-running the build now "bitbake core-image-minimal". It fails for me as I have detailed in my previous emails.

If I manually do:

$ bitbake bash
$ bitbake core-image-minimal

everything succeeds and my image contains 'bash'. But something tells me there's a bug in there somewhere.
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

On Tue, Nov 27, 2012 at 5:39 AM, Eric Bénard <eric@...> wrote:
I confirm the problem when following this procedure step by step.

Thank you, Eric, for the confirmation.

Just to clarify for anyone following along: the problem isn't with
bash or trace-cmd themselves. If I perform the same steps but use
'bash' first, then 'trace-cmd', adding 'bash' succeeds but later
adding 'trace-cmd' causes 'trace-cmd' to fail in the same way 'bash'
did when it was added second.


Re: IMAGE_INSTALL_append workflow

Eric Bénard <eric@...>
 

Hi Trevor,

Le Mon, 26 Nov 2012 21:20:30 -0500,
Trevor Woerner <twoerner@...> a écrit :

On Mon, Nov 26, 2012 at 6:52 PM, Trevor Woerner <twoerner@...> wrote:
I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel =
"linux-yocto-rt"" line might be the culprit.
No, it is not related, this problem doesn't need any fancy
configuration features. This problem is reproducible
with just the plain qemux86 machine and the core-image-minimal image.
Also, before my latest tests I pulled
the latest git repo.

To reproduce this problem:

- use the latest git repositories
- run "source poky/oe-init-build-env qemux86"
- make no modifications to conf/bblayers.conf
- make no changes to conf/local.conf
- run "bitbake core-image-minimal"

After that completes successfully add the following line to your
conf/local.conf:

IMAGE_INSTALL_append = " trace-cmd"

- re-run the build "bitbake core-image-minimal"

This should complete successfully. When it does, modify the last line
of conf/local.conf to be:

IMAGE_INSTALL_append = " trace-cmd bash"

- try re-running the build now "bitbake core-image-minimal". It fails
for me as I have detailed in my previous emails.

If I manually do:

$ bitbake bash
$ bitbake core-image-minimal

everything succeeds and my image contains 'bash'. But something tells
me there's a bug in there somewhere.
I confirm the problem when following this procedure step by step.

with bitbake -e we see that bash is in RDEPENDS and in IMAGE_INSTALL
with bitbake -g we see that bash is not present in any of the
*depends.dot files

Eric


Preempt-rt kernel build for beagleboard

Yu Pan <panyu2000@...>
 

I started looking at Yocto 2 weeks back. Despite the complexity in kernel building, I found it quite hard to locate information on preempt-rt build. I was trying to build linux-yocto-rt for beagleboard from "danny" and the linux-yocto-3.4 kernel, and it seems to be working. I'd like to share how one can do that in this thread.

Since the kernel does not include an official preempt-rt branch for beagleboard yet, I choose to directly use the standard/preempt-rt/base branch. I guess this should work for the preempt-rt kernel, from the fact that the standard kernel (non preempt-rt) used for beagleboard from the standard/beagleboard branch is basically identical to that from the standard/base branch.

Here is what I did.
1. Under poky/meta-yocto-bsp/recipes-kernel/linux, I added a linux-yocto-rt_3.4.bbappend recipe containing the following lines. The SRCREV value used is the same as the one in the base linux-yocto-rt_3.4.bb under poky/meta/recipes/kernel.

  KBRANCH_beagleboard = "standard/preempt-rt/base" 
  SRCREV_machine_beagleboard ?= "5705c8037d2c47938034ead87c70ae3ebef552f7" 
  COMPATIBLE_MACHINE_beagleboard = "beagleboard"

2. Modified the PREFERRED_PROVIDER_virtual/kernel variable in poky/meta-yocto-bsp/conf/machine/beagleboard.conf to "linux-yocto-rt".

3. "bitbake linux-yocto-rt -c menuconfig" to set the Preemption Model to "Fully Preemptible Kernel (RT)".

4. "bitbake linux-yocto-rt"

5. "bitbake core-image-rt" which includes some realtime test programs on top of core-image-minimal.

I did some cyclictest on beagleboard using the generated kernel and image with "/usr/bin/cyclictest -p95 -m". The results did show huge improvement on max latency especially under load.

Hope it helps.

Cheers
Pan Yu


Re: does meta-intel/meta-tlk layer require a README.sources file?

Burton, Ross <ross.burton@...>
 

On 26 November 2012 20:44, Tom Zanussi <tom.zanussi@...> wrote:
The meta-tlk layer isn't a BSP layer - it's a layer used to add the
'time limited kernel' feature to images built from a meta-intel BSP
layer and distributed with that layer e.g. in the downloadable tarballs
available on the Yocto downloads page.

It's a meta-intel-only layer and has no meaning unless coupled with a
meta-intel BSP layer, which does always includes a README.sources of its
own, and so doesn't itself need one.
It's probably worth adding basically this as the README so that anyone
who comes across it knows what it is.

Ross


Re: Best way to support multiple versions of Poky?

Anders Darander
 

* Burton, Ross <ross.burton@...> [121126 14:58]:

On 26 November 2012 13:55, Jerrod Peach <peachj@...> wrote:
build-bundle (git repo with our layers + tools)
|
+-- meta-ourstuff (git submodule, i.e. separate repo locked to a specific
version within build-bundle)
+-- poky (another submodule)
|
+-- poky BB files (i.e. within meta, meta-yocto, etc.)
Guacamayo does something similar, although meta-outstuff isn't a
submodule of build-bundle.
At ChargeStorm we're using a similar scheme to Guacamayo, i.e. we have
our repo with our recipes, bsp's, distro config etc. in our own
meta-*-directories. And the we have oe-core, meta-oe, and/or poky and
whatever layers we're using as submodules.

Being able to branch a "next" branch that switched the poky revision
to the danny RC instead of denzil was very convenient.
Indeed, and also to be able to create a next branch halfway between
denzil and danny, to be able to port / adapt some recipe that required
bigger changes at about the same time those occured in poky-master (or
oe-core master).

Thus, I'm pretty satisfied with our structure for the moment, though
everything can be improved.

Cheers,
Anders

--
Anders Darander
ChargeStorm AB / eStorm AB


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

On Mon, Nov 26, 2012 at 6:52 PM, Trevor Woerner <twoerner@...> wrote:
I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel =
"linux-yocto-rt"" line might be the culprit.
No, it is not related, this problem doesn't need any fancy
configuration features. This problem is reproducible
with just the plain qemux86 machine and the core-image-minimal image.
Also, before my latest tests I pulled
the latest git repo.

To reproduce this problem:

- use the latest git repositories
- run "source poky/oe-init-build-env qemux86"
- make no modifications to conf/bblayers.conf
- make no changes to conf/local.conf
- run "bitbake core-image-minimal"

After that completes successfully add the following line to your
conf/local.conf:

IMAGE_INSTALL_append = " trace-cmd"

- re-run the build "bitbake core-image-minimal"

This should complete successfully. When it does, modify the last line
of conf/local.conf to be:

IMAGE_INSTALL_append = " trace-cmd bash"

- try re-running the build now "bitbake core-image-minimal". It fails
for me as I have detailed in my previous emails.

If I manually do:

$ bitbake bash
$ bitbake core-image-minimal

everything succeeds and my image contains 'bash'. But something tells
me there's a bug in there somewhere.


some questions when writing recipes

"Liu <treebody@...>
 

Dear all,
    I'm learning how to write a recipe recently and I wrote a recipe to build a package from source code.And now I want to add an function to the recipe to make it just unpack the binary and libraries which generated from source code.It seems like the functions "make from src" and "make from extract binaries" in Makefiles.But then I am faced with a question is that how do I tell some recipes to build from src and some just to unpack binaries.
     For example,package C depends on A and B.I bitbake C ,but I want to build A from src code which means do a list of tasks like do_compile,do_install.Meanwhile I want to build B just from binaries which means only unpack the binaries and libraries to the right directory.So is there any good solutions when all wrote in one recipe? Another question is that can I pass a parameter to bitbake using the command like "bitbake C parameter" ?
Best wishes!
----------------------Liu


Re: Wiki Main page terrible sparse

Jeff Osier-Mixon <jefro@...>
 

Hi Maxin - it would be good to coordinate your effort with the rest of
the community. Can you let us know what you have in mind before
starting?

Also, please let me know if you have trouble with access. I don't see
any account requests being held.

thanks

On Fri, Nov 23, 2012 at 6:16 AM, Maxin John <Maxin.John@...> wrote:
Hi Alex,
Hello all,
I can't help but notice that the main page of the Yocto Wiki looks somewhat underwhelming compared to the new site face.
Can we please have a volunteer to update and beautify a bit the main page ?
I am interested in this task. I have already sent a request for access to the Yocto Wiki.

I'd think that we need to list current 1.4 pages, add/verify links to all main sections, and the Yocto logo, etc...
We can discuss the list of activities in this mailing-list or in irc (nickname: maxin)

Cheers,
Alex
Best Regards,
Maxin
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org


Re: IMAGE_INSTALL_append workflow

Trevor Woerner
 

Thank you so much for having a crack at this. Your results have allowed me to dig a bit deeper into this issue.

I'm still trying to narrow down the exact issue but here's what I have so far.

I'm working with the git repository, but I've been playing around with this for about a week, so I'm not 100% up to date. Specifically I'm using:

master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5

Starting with that repository I follow the regular steps:

$ poky/oe-init-build qemux86

then I edit the conf/local.conf to end up with the following (virtually no changes, just the lines at the end):

PARALLEL_MAKE = "-j 8"
MACHINE ??= "qemux86"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
CONF_VERSION = "1"

BB_DANGLINGAPPENDS_WARNONLY = "yes"
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"

then I perform

$ bitbake core-image-minimal

everything goes well. I then add the following line to the end of my conf/local.conf

IMAGE_INSTALL_append = " trace-cmd"

and run

$ bitbake core-image-minimal

everything builds just fine.

Then I modify that last line as follows:

IMAGE_INSTALL_append = " trace-cmd bash"

now when I try to build I get:

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "i586"
TARGET_OS         = "linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3+snapshot-20121126"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta             
meta-yocto       
meta-yocto-bsp    = "master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information)
ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668
Log data follows:
| DEBUG: Executing shell function do_rootfs
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/qemux86...
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/i586...
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all...
|    total:               1      0.000000 MB      2.930406 secs
|    fingerprint:      1104      0.032554 MB      0.063469 secs
|    install:           368      0.000000 MB      0.878790 secs
|    digest:            736      5.357010 MB      0.027508 secs
|    signature:         736      0.000000 MB      1.443277 secs
|    dbadd:             368      0.000000 MB      0.866237 secs
|    dbget:           12620      0.000000 MB      0.018020 secs
|    dbput:             368      3.063072 MB      0.541058 secs
|    readhdr:          3681      6.087218 MB      0.010347 secs
|    hdrload:          1929     10.076294 MB      0.012106 secs
|    hdrget:          70812      0.000000 MB      0.081749 secs
| Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all...
| Processing packagegroup-core-boot...
| Processing trace-cmd...
| Processing bash...
| Unable to resolve package bash
| ERROR: some packages were missing
| ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information)
ERROR: Task 7 (/home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1443 tasks of which 1442 didn't need to be rerun and 1 failed.
No currently running tasks (1442 of 1444)

Summary: 1 task failed:
  /home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Can anyone reproduce this? It doesn't make sense.

Initially when I first saw this problem, I had been using building "core-image-rt" so I thought it had something to do with that image. But my tests from today seem to indicate that it doesn't since I was able to reproduce my problem with "core-image-minimal" too.

I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"" line might be the culprit.


Re: IMAGE_INSTALL_append workflow

Robert P. J. Day
 

On Mon, 26 Nov 2012, Aws Ismail wrote:

Have you also tried this?

IMAGE_INSTALL_append += "foo"
GAAAAAHHHHHH!!! :-)

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Yocto Project Technical Team Meeting

Liu, Song <song.liu@...>
 

When: Tuesday, November 27, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed
 
Note: The GMT offset above does not reflect daylight saving time adjustments.
 
*~*~*~*~*~*~*~*~*~*
 
We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):
 
 
Conference details
Conference name: Yocto Technical Team
Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants: 30
Duration: 60 minutes
Participant passcode: 76994298
Dial-in number: 1.972.995.7777
US Toll Free number: 1.877.561.6828
BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298#
  Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.
Local and Global Access Numbers
 
Country Dial-in number
Australia: 1800 636 843
Czech Republic: 242 430 350
China (Beijing): From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai): From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen): From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities): From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark: 8060 1400
Finland: 09 41333477
France: 0497 275888
Germany: 08161 803232
Holland: 030 2417490
India: BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel: 09 790 6715
Italy: 039 69061234 (039 is local city code not country code)
Japan: From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia: From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway: 2 295 8744
Philippines: From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore: From IP phone dial 3894777
Outside TI use 6389 4777
South Korea: From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden: 08 58755577
Taiwan: From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey: Landline Only dial 0811 288 0001
then enter 877 633 1123
UK: 01604 663003
US: 972 995 7777 or 1877 561 6828
 
Recurring conferences
First scheduled conference: Tue Jun 26, 2012
Recurrence frequency: Weekly - Every 1 week(s) on Tuesday
Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
 
 
 
 


Yocto Project Technical Team Meeting

Liu, Song <song.liu@...>
 

When: Occurs every Tuesday effective 6/26/2012 until 6/18/2013 from 8:00 AM to 9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed
 
Note: The GMT offset above does not reflect daylight saving time adjustments.
 
*~*~*~*~*~*~*~*~*~*
 
We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):
 
 
Conference details
Conference name: Yocto Technical Team
Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants: 30
Duration: 60 minutes
Participant passcode: 76994298
Dial-in number: 1.972.995.7777
US Toll Free number: 1.877.561.6828
BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298#
  Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.
Local and Global Access Numbers
 
Country Dial-in number
Australia: 1800 636 843
Czech Republic: 242 430 350
China (Beijing): From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai): From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen): From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities): From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark: 8060 1400
Finland: 09 41333477
France: 0497 275888
Germany: 08161 803232
Holland: 030 2417490
India: BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel: 09 790 6715
Italy: 039 69061234 (039 is local city code not country code)
Japan: From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia: From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway: 2 295 8744
Philippines: From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore: From IP phone dial 3894777
Outside TI use 6389 4777
South Korea: From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden: 08 58755577
Taiwan: From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey: Landline Only dial 0811 288 0001
then enter 877 633 1123
UK: 01604 663003
US: 972 995 7777 or 1877 561 6828
 
Recurring conferences
First scheduled conference: Tue Jun 26, 2012
Recurrence frequency: Weekly - Every 1 week(s) on Tuesday
Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
 
 
 
 


Agenda: Yocto Project Technical Team Meeting - Tuesday, November 27, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Liu, Song <song.liu@...>
 

Agenda:
 
* Opens collection - 5 min (Song)
* Yocto 1.4 status - 20 min (Song/team)
* SWAT team rotation: Ross -> LaurentiuP
* Opens - 10 min
* Team Sharing - 20 min


-----Original Appointment-----

We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto
IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html

Conference details
Conference name:
Yocto Technical Team
Conference date/start time:
Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants:
30
Duration:
60 minutes
Participant passcode:
76994298
Dial-in number:
1.972.995.7777
US Toll Free number:
1.877.561.6828
BlackBerry users, click this link to join your conference as a participant:
1.972.995.7777x76994298#
 
Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.

Local and Global Access Numbers


Country
Dial-in number
Australia:
1800 636 843
Czech Republic:
242 430 350
China (Beijing):
From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai):
From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen):
From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities):
From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark:
8060 1400
Finland:
09 41333477
France:
0497 275888
Germany:
08161 803232
Holland:
030 2417490
India:
BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel:
09 790 6715
Italy:
039 69061234 (039 is local city code not country code)
Japan:
From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia:
From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway:
2 295 8744
Philippines:
From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore:
From IP phone dial 3894777
Outside TI use 6389 4777
South Korea:
From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden:
08 58755577
Taiwan:
From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey:
Landline Only dial 0811 288 0001
then enter 877 633 1123
UK:
01604 663003
US:
972 995 7777 or 1877 561 6828

Recurring conferences
First scheduled conference:
Tue Jun 26, 2012
Recurrence frequency:
Weekly - Every 1 week(s) on Tuesday
Recurrence ends:
End on Fri Jun 21, 2013, 10:40 AM CDT


Re: IMAGE_INSTALL_append workflow

Aws Ismail <aws.ismail@...>
 

On 11/26/2012 02:04 PM, Eren Türkay wrote:
On Mon, Nov 26, 2012 at 10:47:31AM -0500, Trevor Woerner wrote:
I'm kinda surprised nobody jumped in on this one; either my question
is so silly it isn't worth anyone's time, or I'm the only one who
wants to add packages to an image after a full build. I know my
question has nothing to do with trace-cmd specifically, adding any
package after a full build results in the same problem.
I don't think you are the first person who wants to add a package to image after
the image has been built :)

The obvious problem would have been leading spaces in IMAGE_INSTALL_append but
you explicitly stated its correct. Normally, the class that's responsible for
image creation (image.bbclass) depends on the packages defined in IMAGE_INSTALL
so that the packages are built before the image creation begins.

image.bbclass, line 9
---------------------
RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL}
${ROOTFS_BOOTSTRAP_INSTALL}"

On irc (#oe), Eric Benard tried IMAGE_INSTALL_append = " trace-cmd" after a full
build and reported that it built fine. I'm CCing him.
Have you also tried this?

IMAGE_INSTALL_append += "foo"

Aws\

I believe that it will be better to include your <image> file and the files that
you changed so that it will be easier to debug. Mentioning your layers,
configuration, version of Yocto you use will also be helpful.

Regards,
Eren



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


--