Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] kernel built by buildroot won't boot
Date: Wed, 22 Jul 2009 14:09:08 +0200	[thread overview]
Message-ID: <87bpncdimz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1248251679.3933.11.camel@sven> (Sven Neumann's message of "Wed\, 22 Jul 2009 10\:34\:39 +0200")

>>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:

Hi,

 Sven> We tracked this down to the fact that buildroot passes the
 Sven> TARGET_CFLAGS (with some minor adjustments) to the kernel build
 Sven> as CFLAGS_KERNEL. The problem is that the TARGET_CFLAGS contain
 Sven> "-mtune=iwmmxt -march=iwmmxt", which is fine for the
 Sven> user-space, but you can't build a working kernel with these
 Sven> flags. Not passing any CFLAGS at all solved the problem for us
 Sven> and buildroot now creates a kernel that boots and works nicely.

I don't use the kernel build stuff, but I think it should be fine to
just get rid of it as the kernel doesn't need to link with any user
space libraries or similar.

The kernel is also pretty good about passing the correct gcc flags for
arch variants.

 Sven> Is there a particular reason for passing the TARGET_CFLAGS to the kernel
 Sven> build? Could this perhaps be dropped entirely or at least be made
 Sven> optional?

Care to send a patch?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-07-22 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  8:34 [Buildroot] kernel built by buildroot won't boot Sven Neumann
2009-07-22 12:09 ` Peter Korsgaard [this message]
2009-07-22 12:25   ` [Buildroot] [PATCH] linux26: do not set CFLAGS_KERNEL to TARGET_CFLAGS Sven Neumann
2009-07-22 20:45     ` Peter Korsgaard

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=87bpncdimz.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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