Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel built by buildroot won't boot
Date: Wed, 22 Jul 2009 10:34:39 +0200	[thread overview]
Message-ID: <1248251679.3933.11.camel@sven> (raw)

Hi,

we are developing for an ARM platform. Here are the relevant parts of
our buildroot .config:

BR2_ARM=Y
BR2_iwmmxt=y
BR2_ARM_TYPE="ARM_IWMMXT"
# BR2_ARM_OABI is not set
BR2_ARM_EABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="iwmmxt"
BR2_GCC_TARGET_ARCH="iwmmxt"
BR2_GCC_TARGET_ABI="aapcs-linux"

So far we did compile the kernel ourselves, using the gcc from the
buildroot toolchain. Now we have changed our setup to have buildroot
create the kernel for us. The build succeeds, but the resulting kernel
can not be booted.

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

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


Sven

             reply	other threads:[~2009-07-22  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  8:34 Sven Neumann [this message]
2009-07-22 12:09 ` [Buildroot] kernel built by buildroot won't boot Peter Korsgaard
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=1248251679.3933.11.camel@sven \
    --to=s.neumann@raumfeld.com \
    --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