Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Jul 2005 12:01:05 -0500
From:      Nikolas Britton <nikolas.britton@gmail.com>
To:        =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu>
Cc:        FreeBSD - Questions <freebsd-questions@freebsd.org>
Subject:   Re: FreeBSD 6
Message-ID:  <ef10de9a050727100144fa2600@mail.gmail.com>
In-Reply-To: <42E815EC.20309@t-hosting.hu>
References:  <ef10de9a05072613007ac60130@mail.gmail.com> <42E69B11.6070208@t-hosting.hu> <ef10de9a050726171649b6869@mail.gmail.com> <42E815EC.20309@t-hosting.hu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7/27/05, K=F6vesd=E1n G=E1bor <gabor.kovesdan@t-hosting.hu> wrote:
> Nikolas Britton wrote:
>=20
> >On 7/26/05, K=F6vesd=E1n G=E1bor <gabor.kovesdan@t-hosting.hu> wrote:
> >
> >
> >>Nikolas Britton wrote:
> >>
> >>
> >>
> >>>Is it just me or is -O2 now the default for kernel builds? What about
> >>>-Os, safe to use?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>So is it for me. But if I specify some CFLAGS, for example -O3
> >>-march=3Dathlon64, the
> >>building fails, but CFLAGS mustn't affect the kernel compiling process
> >>afaik. There is
> >>COPTFLAGS for that reason. I've also made a PR about this new, unwanted
> >>behaviour,
> >>but haven't got any answers so yet.
> >>
> >>
> >>
> >
> >You are right, COPTCLAGS is for the kernel only. -O3 is not officially
> >supported for CFLAGS or COPTFLAGS. If you use -O3 for CFLAGS it will
> >break some ports. Also from my experience using anything higher then
> >CPUTYPE=3Dp2 will break ports (like gstreamer).
> >
> >This is what I normally add to my make.conf file:
> >CPUTYPE=3Dp2
> >CFLAGS=3D -Os -pipes
> >COPTFLAGS=3D -Os -pipes
> >#CXXFLAGS=3D don't remember what I set this too, don't use it a lot.
> >
> >If I want a port to build with different settings I just tell it to
> >inline... make CPUTYPE=3Dp4 install clean etc.
> >
> >
> >
> Yes, I know -O3 isn't supported for either, but I didn't mean ports. The
> kernel building
> fails with this:
> CFLAGS=3D-O3 -march=3Dathlon64
> #COPTFLAGS=3D-O3 -march=3Dathlon64   <-This is commenred out!
> And this breaks the kernel compiling. See this:
>=20
> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D83995

Isn't their a way to overide any setting in make.conf by putting it (
-O flags ) inside the kernel config file, I seem to remember doing
something like that in the passed. Or you could do it all inline again
like: nice -20 make -j2 CYPUTYPE=3Dp4 "CFLAGS=3D -Os -pipe"
KERNCONF=3DME_COLONEL buildkernel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a050727100144fa2600>