* [gentoo-dev] Kernel compiling respecting CFLAGS
@ 2003-04-14 15:18 Daniel Armyr
2003-04-14 15:30 ` Jon Portnoy
2003-04-14 15:37 ` Peter Fein
0 siblings, 2 replies; 4+ messages in thread
From: Daniel Armyr @ 2003-04-14 15:18 UTC (permalink / raw
To: gentoo-dev
After quite a few compiles, It seems to me that the compilation of
kernels does not respect CFPAGS or CXXFLAGS settings. Is this true? If
so, is there a reason besides "If people compile the kernel with the
optimizations they want, their kernel will be mangled into oblivion."?
//Daniel Armyr
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] Kernel compiling respecting CFLAGS
2003-04-14 15:18 [gentoo-dev] Kernel compiling respecting CFLAGS Daniel Armyr
@ 2003-04-14 15:30 ` Jon Portnoy
2003-04-14 15:37 ` Peter Fein
1 sibling, 0 replies; 4+ messages in thread
From: Jon Portnoy @ 2003-04-14 15:30 UTC (permalink / raw
To: Daniel Armyr; +Cc: gentoo-dev
Portage doesn't compile the kernel.
On Mon, Apr 14, 2003 at 11:18:59PM +0800, Daniel Armyr wrote:
> After quite a few compiles, It seems to me that the compilation of
> kernels does not respect CFPAGS or CXXFLAGS settings. Is this true? If
> so, is there a reason besides "If people compile the kernel with the
> optimizations they want, their kernel will be mangled into oblivion."?
>
> //Daniel Armyr
>
>
> --
> gentoo-dev@gentoo.org mailing list
--
Jon Portnoy
avenj/irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] Kernel compiling respecting CFLAGS
2003-04-14 15:18 [gentoo-dev] Kernel compiling respecting CFLAGS Daniel Armyr
2003-04-14 15:30 ` Jon Portnoy
@ 2003-04-14 15:37 ` Peter Fein
2003-04-15 3:57 ` Cliff Free
1 sibling, 1 reply; 4+ messages in thread
From: Peter Fein @ 2003-04-14 15:37 UTC (permalink / raw
To: Daniel Armyr; +Cc: gentoo-dev
On Mon, 14 Apr 2003 23:18:59 +0800
Daniel Armyr <daniel.armyr@home.se> wrote:
> After quite a few compiles, It seems to me that the compilation of
> kernels does not respect CFPAGS or CXXFLAGS settings. Is this true? If
> so, is there a reason besides "If people compile the kernel with the
> optimizations they want, their kernel will be mangled into oblivion."?
La la la ....
http://forums.gentoo.org/viewtopic.php?t=24849
--
Peter Fein
pfein@pobox.com
773-575-0694
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] Kernel compiling respecting CFLAGS
2003-04-14 15:37 ` Peter Fein
@ 2003-04-15 3:57 ` Cliff Free
0 siblings, 0 replies; 4+ messages in thread
From: Cliff Free @ 2003-04-15 3:57 UTC (permalink / raw
To: Peter Fein; +Cc: Daniel Armyr, gentoo-dev
According to one of the "Linux Core Kernel Commentary" books, compiling
the kernel with the -O3 flag is a BAD idea. The kernel expects some
functions to be in certain places and using -O3 could cause them to be
inlined when they shouldn't, makeing the kernel unstable or broken.
On Mon, 2003-04-14 at 11:37, Peter Fein wrote:
> On Mon, 14 Apr 2003 23:18:59 +0800
> Daniel Armyr <daniel.armyr@home.se> wrote:
>
> > After quite a few compiles, It seems to me that the compilation of
> > kernels does not respect CFPAGS or CXXFLAGS settings. Is this true? If
> > so, is there a reason besides "If people compile the kernel with the
> > optimizations they want, their kernel will be mangled into oblivion."?
>
> La la la ....
>
> http://forums.gentoo.org/viewtopic.php?t=24849
--
Cliff Free <anaranjado@bellsouth.net>
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-04-15 3:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-14 15:18 [gentoo-dev] Kernel compiling respecting CFLAGS Daniel Armyr
2003-04-14 15:30 ` Jon Portnoy
2003-04-14 15:37 ` Peter Fein
2003-04-15 3:57 ` Cliff Free
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox