Hi Alan

> > create mode 100644 bfd/po-bfd.h
> > create mode 100644 bfd/po64-s390.c
> > create mode 100644 include/po/common.h
> > create mode 100644 include/po/external.h
> > create mode 100644 include/po/internal.h
> > create mode 100644 ld/emulparams/po64_s390.sh
> > create mode 100644 ld/scripttempl/po64_s390.sc
> 
> These are really jarring names to anyone who is accustomed to po files
> as Gettext Portable Object files.  Please change them.  zpo maybe.
> You also have a lot of identifiers starting with po, those also would
> be better as zpo or something else.
Ok. I will change it to zpo

> > +    _bfd_dummy_target,
> > +    _bfd_dummy_target, /* TODO: bfd_po_object_p */
> > +    _bfd_dummy_target,
> > +    _bfd_dummy_target
> 
> Without an object_p function BFD can't read your object files!  So
> this is a write-only format.  You can't inspect symbols, you can't
> objcopy or objdump the files.  How do you test anything?
I know that it's a write only format for now, I'm not yet done with the
reading part in objdump/objcopy and bfd.
For now I'm just testing on the mainframe I've got access to.

Cheers
David