-----<End of build error log extract, cut here>-------------------------------

You will need to correct the problems with your package, update the
CVS repository, cvs rtag the new version, and request a release.

Problems are defined as virtually any output of the build except for a 
limited number of "allowed" fixed strings. Compiler and linker warnings
are considered to be problems in all cases.

If you need to printout messages during your build, there are two things
you can do to prevent receiving these mail messages:

  1) enclose the sections of your makefile that print out the messages
     in ifndef endif blocks testing on NOTRACE. That variable will normally be
     defined as non-null only in Production releases.

  2) include as the first characters of your message, the contents of the
     variable BFPREFIX="-->". Please use the variable so that if needed, we
     can change the string D0-wide without having to edit GNUmakefiles.
     Lines so marked will be ignored by the error mailer.

If you don't consider a given warning a problem, let us know and we'll
put your package into the "not-broken" class. However, until we (D0Rug)
come up with a generalize error parser and agree what should be considered
an "acceptable" error or warning, *all* compiler errors and warnings will
provoke this mail.

D0 Release Managers (d0-release-mgr@fnal.gov)

-----<Build output follows, cut here>-----------------------------------------