From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] kernel compilation vs. -O0
Date: Sat, 29 Mar 2008 06:37:35 +0000 [thread overview]
Message-ID: <1206772655.3224.118.camel@nigel-x60> (raw)
Feeding the kernel zero optimization -O0 breaks the kernel build at
least on x86 with ASM errors.
Any objections to filtering -O0 out?
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel-no-zero-optimization.patch
Type: text/x-patch
Size: 692 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080329/c95e134e/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080329/c95e134e/attachment.pgp
reply other threads:[~2008-03-29 6:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1206772655.3224.118.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--cc=buildroot@busybox.net \
/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