1. 28 Jan, 2014 2 commits
  2. 24 Jan, 2014 3 commits
  3. 21 Jan, 2014 2 commits
  4. 16 Jan, 2014 1 commit
  5. 08 Jan, 2014 3 commits
  6. 02 Jan, 2014 4 commits
    • Richard Purdie's avatar
      bitbake: imagedetailspage: Fix crash with more than 15 layers · 9cea2e49
      Richard Purdie authored
      If you had more than 15 layers the system would crash since one more
      value is added to one array than the other. This fixes the code
      so equal numbers of values are added to the arrays and hence
      doesn't crash when many layers are enabled.
      
      (Bitbake rev: ae420d37fd57a567cf3d2d8096cc9aa28ed01385)
      Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
      9cea2e49
    • Richard Purdie's avatar
      bitbake: parse/ConfHander/BBHandler/utils: Fix cache dependency bugs · 564c687c
      Richard Purdie authored
      Currently bitbake only adds files to its dependency list if they exist.
      If you add 'include foo.inc' to your recipe and the file doesn't exist,
      then later you add the file, the cache will not be invalidated.
      
      This leads to another bug which is that if files don't exist and then
      you add them and they should be found first due to BBPATH, again the
      cache won't invalidate.
      
      This patch adds in tracking of files we check for the existence of so
      that if they are added later, the cache correctly invalidates. This
      necessitated a new version of bb.utils.which which returns a list of
      files tested for.
      
      The patch also adds in checks for duplicate file includes and for now
      prints a warning about this. That will likely become a fatal error at
      some point since its never usually desired to include a file twice.
      
      The same issue is also fixed for class inheritance. Now when a class
      is added which would be found in the usual search path, it will cause
      the cache to be invalidated.
      
      Unfortunately this is old code in bitbake and the patch isn't the
      neatest since we have to work within that framework.
      
      [YOCTO #5611]
      [YOCTO #4425]
      
      (Bitbake rev: 22e6b1c4c4afb27057689bbc94cbdf1f19f93e3d)
      Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
      564c687c
    • Richard Purdie's avatar
      bitbake: data: Fix output inconsistencies for emit_var · 54534a61
      Richard Purdie authored
      VAL = ""     (not shown)
      VAL = " "    (shown as "")
      VAL = " x"   (shown as "x")
      
      would all show up rather differently to what would be expected in the
      bitbake -e output. This fixes things so they appear consistently.
      
      The output for running some shell functions may also change slightly
      but shouldn't change in a way that is likely to cause problems.
      
      [YOCTO #5507]
      
      (Bitbake rev: 9f37afff200d748beddc2a70f55a72c2714e3120)
      Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
      54534a61
    • Richard Purdie's avatar
      bitbake: runqueue/bitbake-worker: Fix dry run fakeroot issues · faef2d95
      Richard Purdie authored
      When using the dry run option (-n), bitbake would still try and fire
      a specific fakeroot worker. This is doomed to failure since it might
      well not have been built.
      
      Add in some checks to prevent the failures.
      
      [YOCTO #5367]
      
      (Bitbake rev: 78ae96e667d3fbb8649fe25eb073e15a99d61cc8)
      Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
      faef2d95
  7. 20 Dec, 2013 1 commit
  8. 13 Dec, 2013 16 commits
  9. 12 Dec, 2013 8 commits