Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] linux .config : override: reassigning to symbol	AEABI
Date: Wed, 29 Jul 2009 15:25:15 +0200	[thread overview]
Message-ID: <20090729132515.GM19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <F81DF98CADE6064F81A746D7C8323593782CAA@fr-ex009.groupinfra.com>

On Wed, Jul 29, 2009 at 02:59:14PM +0200, Courousse, Damien wrote:
> The kernel loading gets stuck after mounting the NFS root : 
> ================================================================
> ....
> IP-Config: Complete:
>      device=eth0, addr=10.84.34.8, mask=255.255.255.192, gw=10.84.34.1,
>      host=debian_test, domain=, nis-domain=(none),
>      bootserver=10.84.34.52, rootserver=10.84.34.52, rootpath=
> Looking up port of RPC 100003/2 on 10.84.34.52
> Looking up port of RPC 100005/1 on 10.84.34.52
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 116K
> Kernel panic - not syncing: Attempted to kill init!
> ================================================================

That smells like an ABI confusion, yes.

> I have configured buildroot to avoid EABI, and everything seems OK on this side in the config files.
> 
> I guess my problem comes from the kernel config, where the EABI symbol is overridden during buildroot compilation: 
> =================================================================
> make[1]: entrant dans le r?pertoire ? /mnt/fractal/buildroot/buildroot-2009.05/project_build_arm/logica_demo/linux-2.6.28 ?
> scripts/kconfig/conf -o arch/arm/Kconfig
> .config:1344:warning: override: reassigning to symbol AEABI
> .config:1345:warning: override: reassigning to symbol IPV6
> ================================================================

Building an OABI toolchain for an EABI kernel doesn't make sense, hence
the configs are brought in sync by buildroot.
target/linux/Makefile.in.advanced is where it happens, and it AEABI
should not be set in the kernel config unless BR2_ARM_EABI is set. Could
you double check?

> Do you think this is a normal behaviour, knowing that I did *not* configure buildroot, uclibc and the kernel for EABI?

No, that shouldn't happen. Could you pastebin your br2 .config
somewhere?


Daniel

  reply	other threads:[~2009-07-29 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 12:59 [Buildroot] linux .config : override: reassigning to symbol AEABI Courousse, Damien
2009-07-29 13:25 ` Daniel Mack [this message]
2009-07-29 13:34   ` [Buildroot] linux .config : override: reassigning to symbolAEABI Courousse, Damien
     [not found]   ` <F81DF98CADE6064F81A746D7C8323593782CAC@fr-ex009.groupinfra.com>
2009-07-29 13:42     ` Daniel Mack
2009-07-29 13:59       ` [Buildroot] linux .config : override: reassigning tosymbolAEABI Courousse, Damien
2009-07-29 14:26         ` Daniel Mack
2009-07-29 16:07           ` Courousse, Damien
2009-07-29 17:30             ` Daniel Mack
2009-07-31 10:20             ` Thomas Petazzoni
2009-07-31 15:57               ` Courousse, Damien
2009-07-29 18:59 ` [Buildroot] linux .config : override: reassigning to symbol AEABI Peter Korsgaard
2009-07-31  9:33   ` Courousse, Damien

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=20090729132515.GM19257@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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