Miles Lane wrote:
Well, from the web page referenced at the top of this message, you
can see that they are already aware of these issues:
Cons:
* It breaks current upstream kernel builds and potentially
other direct usages of gcc. Kernel is by far the most important use
case. Upstream should change the default options to build with
-fno-stack-protector by default.
* It is not conformant to upstream gcc behaviour.
I don't see why the kernel should have to insert compile flags to
counteract any random non-default compile flags that the system may
decide to insert. I think the way Ubuntu has done this is broken, they
are essentially changing the default settings on the compiler in a way
which breaks the kernel due to needing external libraries.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]