Thanks, David!  I have no interest in running pgen on the target/host.  My only interest is building python and its various modules to run on my embedded host.  I do not want to develop Python on the embedded host.  Unfortunately, the build process requires Parser/pgen to build the grammar files, which are needed for several object files.  Here's the relevant snippet from the Makefile.pre.in:

$(GRAMMAR_H): $(GRAMMAR_INPUT) $(PGENSRCS)
        @$(MKDIR_P) Include
        $(MAKE) $(PGEN)
        $(PGEN) $(GRAMMAR_INPUT) $(GRAMMAR_H) $(GRAMMAR_C)
$(GRAMMAR_C): $(GRAMMAR_H) $(GRAMMAR_INPUT) $(PGENSRCS)
        $(MAKE) $(GRAMMAR_H)
        touch $(GRAMMAR_C)

$(PGEN):    $(PGENOBJS)
        $(CC) $(OPT) $(LDFLAGS) $(PGENOBJS) $(LIBS) -o $(PGEN)

Parser/grammar.o:   $(srcdir)/Parser/grammar.c \
                $(srcdir)/Include/token.h \
                $(srcdir)/Include/grammar.h
...
Python/compile.o Python/symtable.o Python/ast.o: $(GRAMMAR_H) $(AST_H)

If there is a way to eliminate the need for Parser/pgen to run on the build system to cross-compile the default "all" target, that would be great. ... I'll experiment with "make touch". ... Thanks!