Re: Kernel Build(s) broken in -Current

2002-02-28 Thread Julian Elischer

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 process. Yes the file(s) with errors can be
> edited my hand to set the offending variable to a 'default' value, but its
> really, really annoying to have to do so…. Could the make file(s) for
> -Current be set back to the default of treating 'warning(s)' as warnings
> and not errors ??……..
> Glenn Gombert
> [EMAIL PROTECTED]
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel Build(s) broken in -Current

2002-02-28 Thread Brooks Davis

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
> edited my hand to set the offending variable to a 'default' value, but its
> really, really annoying to have to do so…. Could the make file(s) for
> -Current be set back to the default of treating 'warning(s)' as warnings
> and not errors ??……..

If you're going to run current, you need to read this list.  The problems
have largly been fixed, update your sources and read UPDATING for more
info.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4



msg35532/pgp0.pgp
Description: PGP signature


Kernel Build(s) broken in -Current

2002-02-28 Thread Glenn Gombert

  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 its
really, really annoying to have to do so…. Could the make file(s) for
-Current be set back to the default of treating 'warning(s)' as warnings
and not errors ??……..
Glenn Gombert
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message