On Mon, May 06, 2002 at 07:31:30AM +0200, Jeroen Ruigrok/asmodai wrote:
> -On [20020506 00:30], Kris Kennaway ([EMAIL PROTECTED]) wrote:
> >On Sun, May 05, 2002 at 02:42:22PM +0200, Jeroen Ruigrok/asmodai wrote:
> >
> >> I definately do not call libiberty kernel related.
> >> Nor do we, by default, advocate NO_WERROR.  So in effect, we broke moving
> >> from older versions to newer versions of CURRENT.
> >
> >Can you track down what the actual cause of the breakage is?  I can't
> >immediately see why compiling on an older version should cause extra
> >warnings, because the build should be using the up-to-date system
> >headers and code.
> The libiberty Makefile sets WARNS higher than 0, which effectively [through
> share/mk] also sets -Werror since NO_WERROR is not defined.

Yes, but why is this only a problem for upgrade builds from older
systems?  That's what doesn't sound right to me.


Attachment: msg38064/pgp00000.pgp
Description: PGP signature

Reply via email to