how to copy NTP parser files verbatim from 4.2.8p10 to 4.2.8p13?
Robert P. J. Day
here's hoping someone has gone through this and can summarize what i
need to do; i'll try to keep it short.
migrating all sorts of stuff from (effectively) morty project to
(effectively) zeus, and currently moving from ntp_4.2.8p10 to
ntp_4.2.8p13, the only complication being that, way back when, the p10
parser was extended to recognize two new (proprietary) command-line
options; thus, at the time, it's clear that yacc was run to generate
new parser files, which have worked just fine all this time, so i have
a solution for p10.
so far, i've added all the underlying support code for these
additional options, and all of that compiles just fine, so everything
needed to *support* the two new options is in place -- new structures
have been added, existing structures have been extended, new functions
are in place, etc etc etc. all that looks good.
the only thing missing is the final bit to support the two new
run-time options, but i've been told that there is no need to re-run
yacc to re-generate the parser files, as i can just take them verbatim
from the old p10 recipe (and i don't think i have a choice since i
can't get [b]yacc to run anyway, as it simply generates a usage
so all i'm after is, needing to avoid running yacc again, to know
what i need to steal from the p10 patches. i have patches touching all
of (and more):
i've tried to selectively copy what look like the appropriate files
into the appropriate locations but, no matter what i do, the build
process insists on running byacc again, and chokes.
so focusing exclusively on the parser component, is there a simple
list of what i need to copy in/patch verbatim to effect the same
changes without the build trying to regenerate the parser files? once
i have that, i can obviously add the final support code that
recognizes the new parser tokens.
thoughts? am i even looking at this the right way?