[bitbake-devel] Bitbake exception when recipe path contains a blank

[Mark Hatle]

It's a known issue, spaces are not allowed in path names.

There should already be checks without OE for this, but I'm guessing that this
is firing before those checks (or those checks are incomplete.)

I believe this is in sanity.bbclass, "chcek_sanity_everybuild" function, about
line 837 in the current master.

The check appears to only be scanning 'oeroot'.  Perhaps a new check for the
layers either inside of the sanity (if it's run early enough) or in bitbake
itself is needed.

Note, the big below should likely get fixed.  Any time the system throws an
exception like this, I'd consider it a bug.

--Mark

On 12/22/19 8:29 AM, Konrad Weihmann wrote:
> Hi All,
> 
> I experienced a strange issue recently - currently I'm using bitbake 
> 1.44.0 as it comes with Yocto:zeus-release, but it really doesn't 
> matter, as the underlying code didn't change within the last few years.
> 
> I created a recipe (nothing special, just some files and some compiler 
> instructions).
> Important is that SRC_URI contains at least one file://-entry.
> 
> When I tried to run the recipe build crashed with the following exception
> 
>    File "/build/poky/bitbake/lib/bb/checksum.py", line 103, in 
> FileChecksumCache.get_checksums(filelist='/build/meta-something/test-recipe 
> /test-recipe/mydistro/a.file:False ', pn='test-recipe'):
> 
>               for pth in filelist.split():
>      >            exist = pth.split(":")[1]
>                   if exist == "False":
> IndexError: list index out of range
> 
> A look at the filelist argument shows a strange first item (missing ':').
> 
> After some debugging it went done to that the path to the recipe was
> 
> "/build/meta-something /test-recipe" instead of 
> "/build/meta-something/test-recipe".
> 
> After removing the blank in the path, everything went well.
> 
> Maybe that's one for the initial parsing to issue a warning, that the 
> path to a recipe is corrupted.
> 
> Does anyone encountered that before? Any thoughts on how and where to 
> fix this?
> 
> Regards
> 
> Konrad
> 
>