Date: Mon, 6 May 2002 07:31:30 +0200 From: Jeroen Ruigrok/asmodai <asmodai@wxs.nl> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freebsd.org Subject: Re: Breaking old compilation paths Message-ID: <20020506053130.GJ66061@daemon.ninth-circle.org> In-Reply-To: <20020505151535.A29157@xor.obsecurity.org> References: <20020504181205.GG66061@daemon.ninth-circle.org> <20020505124222.GT66061@daemon.ninth-circle.org> <20020505151535.A29157@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-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. I would need to see if it is something libc related or something which causes the function failure. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@wxs.nl, finger asmodai@ninth-circle.org http://www.softweyr.com/asmodai/ | http://www.tendra.org/ Where does the world end if the enternal optimist loses faith..? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020506053130.GJ66061>