Re: -fno-strict-aliasing

From: Bruno T. <bmrk_at_terra.com.br>
Date: Mon, 9 Feb 2004 03:31:44 -0200
On Mon, 9 Feb 2004 06:04:14 +0100
Melvyn Sopacua <freebsd-current_at_webteckies.org> wrote:

> On Monday 09 February 2004 05:59, Bruno T. wrote:
> > On Sun, 8 Feb 2004 20:32:17 -0800
> >
> > Kris Kennaway <kris_at_obsecurity.org> wrote:
> > > On Mon, Feb 09, 2004 at 02:28:20AM -0200, 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.
> > >
> > > Don't do that then :-)
> > >
> > > Kris
> >
> > yeah, i just didn't want to change any code without being familiar with the
> > whole stuff.
> 
> What Kris means is that -O2 for kernel and base builds are not supported. It's 
> documented in (/usr/share/examples)/etc/make.conf.
> 
> Since you're coming from Linux, you prolly wanna read make(1) manpage (make != 
> GNU make) and browse through /usr/share/mk.
> The developers handbook on the website is also a good start.
> -- 
> Melvyn

I see, thanks for pointing that.:)
Received on Sun Feb 08 2004 - 20:27:19 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:42 UTC