On 8/24/16 9:17 AM, Jérémy Rosen wrote: > > > On 24/08/2016 16:13, Mark Hatle wrote: >> >> Make often has a rule looking at the time stamp of specific files and >> re-running >> specific autotools if they are 'out of date'. That COULD be the cause of the >> errant call to gcc? > that would make sense... >> >> I have not observed the above occurring -- but the key thing is that syck >> needs >> to be cleaned of the generated files. We don't want to run any host commands >> other then clean it. >> >> If you have to replace it with something else, you will need to identify all >> of >> the files that need to be cleaned and manually remove them avoiding the >> distclean call. >> >> Easiest way to do that.... extract the source for syck, back it up, run the >> make >> distclean.. compare the difference and use that list as a replacement >> 'cleanup' >> command. > > That wouldn't be very robust to future change in syck, i'm afraid... but > i'll have a look.
There is nothing robust about this change for future work. Future versions will have to do the work in a different way -- and hopefully won't have pre-built crap slipped into the download that we have to cleanup. So I have no concern about future proofing this, as I know the next integration -will- be different in this case. --Mark >> >> --Mark >> >> > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
