Date: Sun, 5 May 2002 22:43:55 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Jeroen Ruigrok/asmodai <asmodai@wxs.nl> Cc: Kris Kennaway <kris@obsecurity.org>, current@freebsd.org Subject: Re: Breaking old compilation paths Message-ID: <20020505224355.B39572@xor.obsecurity.org> In-Reply-To: <20020506053130.GJ66061@daemon.ninth-circle.org>; from asmodai@wxs.nl on Mon, May 06, 2002 at 07:31:30AM %2B0200 References: <20020504181205.GG66061@daemon.ninth-circle.org> <20020505124222.GT66061@daemon.ninth-circle.org> <20020505151535.A29157@xor.obsecurity.org> <20020506053130.GJ66061@daemon.ninth-circle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, May 06, 2002 at 07:31:30AM +0200, Jeroen Ruigrok/asmodai wrote: > -On [20020506 00:30], Kris Kennaway (kris@obsecurity.org) 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. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE81hgbWry0BWjoQKURArFLAKCxNiL5q+Qsit5oybqscaVyfLoi5QCg08aX gjgc/SNs5zEjKCJwtQyl8JI= =FFNY -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020505224355.B39572>