On 10/11/16 11:50 AM, Yuanjie Huang wrote: > The generated parser contains huge hunks of code actually shipped with bison, > so > I think we should also expect some semantic difference.
Exactly the problem. Unless the plural.y has been modified, we should not be regenerating the .c file as shipped by glibc. It has the possibility of introducing problems.... but the immediate concern is the non-determinism where some builds rebuild, some do not. --Mark > Yuanjie > > On 10/11/2016 05:17 PM, Burton, Ross wrote: >> >> On 11 October 2016 at 09:37, Mark Hatle <mark.ha...@windriver.com >> <mailto:mark.ha...@windriver.com>> wrote: >> >> My understanding of the issue is that the extraction of the plural.c and >> plural.y files happens so quickly that it is unclear to make if one is >> older >> then the other -- so it sometimes uses bison to rebuild the plural.c. >> This >> produces a non-deterministic build. >> >> >> Surely the rebuilt plural.c should be identical to the shipped one? >> (semantically if not literally) >> >> Ross > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
