Recipes with SRC_URI in .inc file and checksum in bb file
The specific case I am looking at is fftw in meta-oe, ,but I believe this is a general problem.
The fftw recipe has a .inc file that includes the SRC_URI to a tarball and bb files that build packages with slightly different compile options. The tarball checksums are in the version specific bb files.
I am on the process of updating the fftw recipes to the most recent version. Along the way I noticed it looks like the checksum test is being ignored. The only way I can get it to fail is to remove all the checksum entries from the bb files.
Something needs fixing and I'd like to know what we want in the recipes before I submit the fixes, even if bitbake is broken :)
Should the checksums move to the .inc file? (bad since that makes the .inc file version specific). Should they be duped in each recipe? (Annoying and doesn't really work) Maybe another version specific include? (likely won't work, but could be fixed)
Philip
Quoted 5 lines · Philip Balister
I am on the process of updating the fftw recipes to the most recent version. Along the way I noticed it looks like the checksum test is being ignored. The only way I can get it to fail is to remove all the checksum entries from the bb files.
I've got this kind of problems when I have made several iterations of
the recipe update. In my case the explanation has always been that first test already downloaded the file, so no matter what I do to checksums after that, there's no download + checksum check on later tests.
Remove file and <file>.done from download, + 'bitbake <recipe> -c clean'
- ML
Quoted 7 lines · Marko Lindqvist
Quoted 5 lines · Philip Balister
I am on the process of updating the fftw recipes to the most recent version. Along the way I noticed it looks like the checksum test is being ignored. The only way I can get it to fail is to remove all the checksum entries from the bb files.
Quoted 6 lines
I've got this kind of problems when I have made several iterations of
the recipe update. In my case the explanation has always been that first test already downloaded the file, so no matter what I do to checksums after that, there's no download + checksum check on later tests.
Remove file and <file>.done from download, + 'bitbake <recipe> -c clean'
I uderstand that, but the other problem is even with a new download, the checksum check is ignored if there are checksum entries in more than one bb file.
Philip
Quoted 15 lines · Philip Balister
Quoted 7 lines · Marko Lindqvist
Quoted 5 lines · Philip Balister
I am on the process of updating the fftw recipes to the most recent version. Along the way I noticed it looks like the checksum test is being ignored. The only way I can get it to fail is to remove all the checksum entries from the bb files.
Quoted 6 lines
I've got this kind of problems when I have made several iterations of
the recipe update. In my case the explanation has always been that first test already downloaded the file, so no matter what I do to checksums after that, there's no download + checksum check on later tests.
Remove file and <file>.done from download, + 'bitbake <recipe> -c clean'
Quoted 3 lines
I uderstand that, but the other problem is even with a new download, the checksum check is ignored if there are checksum entries in more than one bb file.
Multiple checksums in different .bb files for the same filename?
Cheers,
Richard