Date
1 - 3 of 3
: When compiling code, how to make a package not hash checked?
Quentin Schulz
Hi Byron,
On Tue, Nov 10, 2020 at 09:09:05PM +0800, ouyangxuan10@... wrote:
Can you send us the content of the log of the second command please?
Basically, two possible ways this happens:
1. you modified the recipe while bitbake was running. Solution => don't
do that.
2. bitbake parses tasks multiple times during a run, therefore, if a
variable changes between parses your task will have a different hash.
This usually happens with DATETIME. If you don't absolutely need this
variable, remove it or find a replacement. If you have to, I think the
vardepsexclude variable flag is the way to do it?
Quentin
On Tue, Nov 10, 2020 at 09:09:05PM +0800, ouyangxuan10@... wrote:
Dear all,Did you execute the commands that were suggested in the log you sent?
I would like to ask the reasons for the following problems and how to solve them? When compiling a program, how to make a package not hash checked?
Can you send us the content of the log of the second command please?
Basically, two possible ways this happens:
1. you modified the recipe while bitbake was running. Solution => don't
do that.
2. bitbake parses tasks multiple times during a run, therefore, if a
variable changes between parses your task will have a different hash.
This usually happens with DATETIME. If you don't absolutely need this
variable, remove it or find a replacement. If you have to, I think the
vardepsexclude variable flag is the way to do it?
Quentin
ouyangxuan10@163.com
hi Quentin,
At 2020-11-10 21:16:15, "Quentin Schulz" <quentin.schulz@...> wrote: >Hi Byron, > >On Tue, Nov 10, 2020 at 09:09:05PM +0800, ouyangxuan10@... wrote: >> Dear all, >> >> >> I would like to ask the reasons for the following problems and how to solve them? When compiling a program, how to make a package not hash checked? >> > >Did you execute the commands that were suggested in the log you sent? > >Can you send us the content of the log of the second command please?>This is another package with the same problem:(Run the above command.)the log in locked-sigs.incI would like to ask, is there any way to separate this package from the verification function?>Basically, two possible ways this happens: > 1. you modified the recipe while bitbake was running. Solution => don't > do that. > 2. bitbake parses tasks multiple times during a run, therefore, if a > variable changes between parses your task will have a different hash. > This usually happens with DATETIME. If you don't absolutely need this > variable, remove it or find a replacement. If you have to, I think the > vardepsexclude variable flag is the way to do it? >>QuentinThanks,Byron