Hi everybody,
We have recently installed an automated build system in our company and occasionally there is a problem when U-Boot is built. One build will work the other will not without any changes to the sources (it is not: 1 work, then other fail... it is more like 3 may work the 4 will not but the 5 will). Our build system guy says that the problem is probably a race condition with a dependency in the U-Boot make.
Here is the error that trigger the failure. *[09:23:58]:* */home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/.depend:73: *** multiple target patterns. Stop.* *[09:23:58]:* *make: *** [/home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/start.o] Error 2* *[09:23:58]:* */home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/.depend:73: *** multiple target patterns. Stop.* *[09:23:58]:* *make: *** Waiting for unfinished jobs....* *[09:23:58]:* *make: *** [/home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/libmpc5xxx.a] Error 2* *[09:24:01]:* *Process exited with code 2*
It is not extremely problematic because everything is automated and next build after the failing one will work (when it is this error), but it's only that we get a notification email when a build fail and we are afraid that our developers will take the failure as a "Boy Who Cried Wolf"... if you know what I mean.
Is there a way to fix this ? It could be putting some "sleep" somewhere...
Any suggestion ?
Sylvain
* Also, upgrading U-Boot is not an option... since we don't have the need nor resources to port a new version of U-Boot to this product. So please don't suggest that.