Mark Goldfinch: > Can someone clarify to me why y.tab.c is included within the bash source > tree if it is generated from parse.y? > > If one looks in the FreeBSD ports tree, they're deliberately taking the > initiative to touch parse.y to ensure that y.tab.c is always rebuilt.
They also have a dependency on the bison port, because parse.y does not build correctly with FreeBSD's yacc(1). You end up with a bash that has broken $(...) parsing. Same issue on OpenBSD, where the port doesn't touch parse.y because there is no need to. > If y.tab.c's timestamp ends up being newer than parse.y, Why would this happen? > a patch which (correctly) only patches parse.y, ... will cause parse.y to have a newer timestamp. -- Christian "naddy" Weisgerber na...@mips.inka.de
