From: Kevin Winchester <kjwinchester@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: arjan@linux.intel.com, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54()
Date: Tue, 06 May 2008 20:09:29 -0300 [thread overview]
Message-ID: <4820E529.2030801@gmail.com> (raw)
In-Reply-To: <20080506.133416.241365936.davem@davemloft.net>
David Miller wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Tue, 06 May 2008 12:49:33 -0700
>
>> this is weird; something is adding ANOTHER -fstack-protector to the (effective) gcc
>> flags.. which might be overriding the -fstack-protector-all setting.
>>
>> I wonder if this is a distro special ;(
>
> Ubuntu adds -fstack-protector to the GCC command line.
>
> But I've been able to override it trivially when, for example, doing
> GCC builds, by simply adding -fno-stack-protector.
I assume adding -fno-stack-protector would not really be an option in
this case (since if I understand correctly it would be appended to the
end of the flags which would turn the option off).
I guess I'll be figuring out how to build my own gcc...
--
Kevin Winchester
next prev parent reply other threads:[~2008-05-06 23:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 23:58 linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54() Kevin Winchester
2008-05-01 0:01 ` Arjan van de Ven
2008-05-01 0:24 ` Kevin Winchester
2008-04-30 7:27 ` Arjan van de Ven
2008-05-01 22:37 ` Kevin Winchester
2008-05-01 11:33 ` Arjan van de Ven
2008-05-03 23:22 ` Kevin Winchester
2008-05-06 19:49 ` Arjan van de Ven
2008-05-06 20:34 ` David Miller
2008-05-06 23:09 ` Kevin Winchester [this message]
2008-05-06 23:10 ` Arjan van de Ven
2008-05-06 23:32 ` Arjan van de Ven
2008-05-06 23:35 ` Kevin Winchester
2008-05-06 23:38 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4820E529.2030801@gmail.com \
--to=kjwinchester@gmail.com \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox