Date: Wed, 12 Apr 2006 13:43:33 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Jim Stapleton <stapleton.41@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: make buildword problem/documentation Message-ID: <20060412104333.GA34707@gothmog.pc> In-Reply-To: <80f4f2b20604111127y6d95504br20cb723c9fc4c34a@mail.gmail.com> <20060411181025.GA45274@gothmog.pc> References: <80f4f2b20604111026i93e19e2jd3360b712db888ae@mail.gmail.com> <20060411193805.P88998@erika.hostname.nu> <80f4f2b20604111050s69ab2a35t8bfc90d4a0876baa@mail.gmail.com> <20060411181025.GA45274@gothmog.pc> <80f4f2b20604111127y6d95504br20cb723c9fc4c34a@mail.gmail.com> <80f4f2b20604111026i93e19e2jd3360b712db888ae@mail.gmail.com> <20060411193805.P88998@erika.hostname.nu> <80f4f2b20604111050s69ab2a35t8bfc90d4a0876baa@mail.gmail.com> <20060411181025.GA45274@gothmog.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-04-11 21:10, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: > On 2006-04-11 17:50, Jim Stapleton <stapleton.41@gmail.com> wrote: > > ahh, thanks everyone, I was looking through the document, and focused > > on finding "buildworld". > > > > Still, anyone know why those particular cflags would cause problems? > > Don't use arbitrary CFLAGS in `make.conf'. The build is already > complicated enough and careful steps have to be taken, without the > introduction of random flags. On 2006-04-11 18:27, Jim Stapleton <stapleton.41@gmail.com> wrote: > ok, thanks, I won't worry about it then. Cool. > I just like to have everything as optimised as possible. Guess it'll > have to wait here... There are cases when things break in one or another way if you enable optimizations for all the builds, in make.conf. The warning near the description of CFLAGS in `/usr/share/examples/etc/make.conf' is there exactly to avoid this sort of thing: # Note that optimization settings other than -O and -O2 are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to "-O" or -O2 before submitting bug # reports without patches to the developers. So, unless there is a measurable performance gain which doesn't also result in strange build- or runtime errors, I guess you don't need to worry about it too much :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060412104333.GA34707>