POT file for cpplib

[Paolo Bonzini]

> Why the Makefile.am change to add an all-local rule?  I figured out that 
> this is automake magic, but since no other directory in gcc, binutils, 
> or gdb has a similar Makefile rule, it isn't clear why this is right for 
> libcpp.

The all-local specifies additional commands to be run when "all" is run.

You can see that libjava uses mostlyclean-local, clean-local, 
distclean-local, install-data-local.  libstdc++-v3 uses all-local for a 
similar purpose: it has

all-local: all-local-$(USE_NLS)

all-local-no:
	# Do nothing

all-local-yes: $(LOCALE_OUT)
	...

(These were posted to gcc as part of the thread, I have already sent 
them to gcc-patches as well and I'll post a comment there saying that I 
committed it).

Paolo