this was fixed.. (many warnings removed)
try resup and reconfig
On Thu, 28 Feb 2002, Glenn Gombert wrote:
> Apparently a recent change in the make file(s) in -Current causes normal
> warning messages to be treated as errors (for un-initialized variables) for
> example, which stops the build p
On Thu, Feb 28, 2002 at 06:31:14PM -0500, Glenn Gombert wrote:
> Apparently a recent change in the make file(s) in -Current causes normal
> warning messages to be treated as errors (for un-initialized variables) for
> example, which stops the build process. Yes the file(s) with errors can be
> e
Apparently a recent change in the make file(s) in -Current causes normal
warning messages to be treated as errors (for un-initialized variables) for
example, which stops the build process. Yes the file(s) with errors can be
edited my hand to set the offending variable to a 'default' value, but i
