Skip to contentSkip to conversation

Debugging overrides

DISCUSSION Gary Thomas 2 participants 4 messages May 4, 2011 – May 5, 2011

lore
Share & tools
lore
#0 lore raw

I'm having trouble getting some overrides to work and would like some ideas how to debug/troubleshoot.

I have this [layered] setup
meta-targetA/

    packages/
      netbase/
        netbase_4.45.bbappend
        netbase-4.45/
          targetA/
            interfaces

Similarly for targetB.

My .bbappend file (identical in both trees) looks like this:

  -----------------------------------------------------------------------------------
  THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
  FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
  PACKAGE_ARCH = "${MACHINE_ARCH}"
  -----------------------------------------------------------------------------------

I've traced through this with -DDD and on one target, I can see the fetcher finding the files in my layer. On a different target, it only finds the files in the main meta/recipes-core/netbase tree

Any suggestions on where I look to understand what's going on?

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 21 lines · Gary Thomas

I'm having trouble getting some overrides to work and would like some ideas how to debug/troubleshoot.

I have this [layered] setup
meta-targetA/
packages/
netbase/
netbase_4.45.bbappend
netbase-4.45/
targetA/
interfaces
Similarly for targetB.

My .bbappend file (identical in both trees) looks like this:

-----------------------------------------------------------------------------------
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:" PACKAGE_ARCH = "${MACHINE_ARCH}"
-----------------------------------------------------------------------------------

Quoted 5 lines

I've traced through this with -DDD and on one target, I can see the fetcher finding the files in my layer. On a different target, it only finds the files in the main meta/recipes-core/netbase tree

Any suggestions on where I look to understand what's going on?

'strace' is my friend :-) It turns out that I had some layering problems which caused the wrong packages/netbase tree to be searched. I ran strace on 'bitbake netbase' and was able to see the erroneous file/path searches which pointed out my problem.

All is well now.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#2 lore raw
Quoted 14 lines · Gary Thomas
Quoted 14 lines

My .bbappend file (identical in both trees) looks like this:

-----------------------------------------------------------------------------------
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:" PACKAGE_ARCH = "${MACHINE_ARCH}"

-----------------------------------------------------------------------------------

I've traced through this with -DDD and on one target, I can see the fetcher finding the files in my layer. On a different target, it only finds the files in the main meta/recipes-core/netbase tree

Quoted 6 lines
Quoted 1 line

Any suggestions on where I look to understand what's going on?

'strace' is my friend :-)  It turns out that I had some layering problems which caused the wrong packages/netbase tree to be searched. I ran strace on 'bitbake netbase' and was able to see the erroneous file/path searches which pointed out my problem.

Okay, what sort of layer tooling would have helped you identify this problem without strace? :)

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#3 lore raw
Quoted 17 lines · Chris Larson
Quoted 16 lines · Gary Thomas
Quoted 15 lines

My .bbappend file (identical in both trees) looks like this:

-----------------------------------------------------------------------------------
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:" PACKAGE_ARCH = "${MACHINE_ARCH}"

-----------------------------------------------------------------------------------

I've traced through this with -DDD and on one target, I can see the fetcher finding the files in my layer. On a different target, it only finds the files in the main meta/recipes-core/netbase tree

Any suggestions on where I look to understand what's going on?

Quoted 7 lines
Quoted 4 lines

'strace' is my friend :-) It turns out that I had some layering problems which caused the wrong packages/netbase tree to be searched. I ran strace on 'bitbake netbase' and was able to see the erroneous file/path searches which pointed out my problem.

Okay, what sort of layer tooling would have helped you identify this problem without strace? :)

Hard to say. What I was really hoping for was basically what strace gave me - the list of candidate files which were being considered to satisfy the SRC_URI. Since the file I wanted was coming from my target layer, what I needed to figure out was why it wasn't on the list.

One thing that should be pretty useful to glean is that bitbake chose meta-targetB/packages/netbase/netbase_4.45.bbappend instead of the one from meta-targetA. Note: this was my error, I had two layers which contained more or less the same structure enabled. This data was in the -DDD dump, but it wasn't obvious enough for me to catch!

Some way to know where are the pieces for some recipe come from, and perhaps the candidates considered as well, would help a lot. I've run into questions/confusions with layers before (bug #807) and this error was very similar.

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------