Hi Nicolas,
GMP is not a dependency for valgrind. I had successfully built valgrind using bitbake before attempting to build gmp, which is an entirely independent package. My attempt to build gmp didn't succeed. Now, when I moved back to valgrind building the problem occurred. I don't understand why gmp is coming into picture.
By <recipe> do you mean the associated .bb file..?
Thanks, Anil
On 27 February 2014 14:34, Nicolas Dechesne nicolas.dechesne@linaro.orgwrote:
Anil,
On Thu, Feb 27, 2014 at 8:54 AM, Anil Singhar anil.singhar@linaro.org wrote:
Now when I switch between these two activities (i.e building valgrind and building gmp), bitbake is mixing things up as follows. Could anyone help
me
on how to get rid of this behavior. As it can be seen, when I use
"bitbake
valgrind" it is trying to pull gmp code and is failing. What should I
doing
to do a clean build? I thought bitbake take the package name and confines its tasks only to that package and should never look at the .bb file of another package, right?
no, this is not correct.
bitbake <recipe>
will first build all dependencies for <recipe>, then it will build <recipe>
so, the gmp issue needs to be addressed first.
nico