From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 05:18:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A29316A4CE; Mon, 9 Feb 2004 05:18:51 -0800 (PST) Received: from chiapa.terra.com.br (chiapa.terra.com.br [200.154.55.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64AAC43D1F; Mon, 9 Feb 2004 05:18:51 -0800 (PST) (envelope-from bmrk@terra.com.br) Received: from sucre.terra.com.br (sucre.terra.com.br [200.154.55.134]) by chiapa.terra.com.br (Postfix) with ESMTP id 04404EC573; Mon, 9 Feb 2004 11:18:50 -0200 (BRST) Received: from pyro.convolution.ti (unknown [200.149.135.186]) (authenticated user bmrk) by sucre.terra.com.br (Postfix) with ESMTP id 7D2CA3C104; Mon, 9 Feb 2004 11:18:49 -0200 (BRST) Date: Mon, 9 Feb 2004 11:23:18 -0200 From: "Bruno T." To: David Schultz Message-Id: <20040209112318.52058962@pyro.convolution.ti> In-Reply-To: <20040209070700.GA2342@VARK.homeunix.com> References: <20040209022820.00faa408@pyro.convolution.ti> <20040209070700.GA2342@VARK.homeunix.com> X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.ORG Subject: Re: -fno-strict-aliasing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 13:18:51 -0000 On Sun, 8 Feb 2004 23:07:00 -0800 David Schultz wrote: > On Mon, Feb 09, 2004, Bruno T. wrote: > > Hi everyone. > > i'm pretty new to bsd, but i have some background in linux development > > and for what i have seen until now, i must say that -CURRENT is rather impressive, congrats ! > > > > I was rebuilding my base sys and noticed that any compiler flag > > that implies -fstrict-aliasing (like -O2) would break some few things, > > adding "-fno-strict-aliasing" to "CFLAGS+=" in these makefiles > > solves the problem for now. > > > > usr.sbin/kldxref/Makefile > > lib/libc/Makefile > > lib/libpam/Makefile > > libexec/ypxfr/Makefile > > usr.sbin/rpc.yppasswd/Makefile > > I assume the problem is some specific C sources, rather than the > Makefiles themselves. It's generally known that there are a few > aliasing problems lurking around the source tree that break > -fstrict-aliasing, and patches to fix them would be appreciated. Thanks, I'll cook up that patches later tonight and send them back here. previously i just changed the makefiles because i haven't a good perspective of the whole base system stuff.:)