From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] linux .config : override: reassigning to symbolAEABI
Date: Wed, 29 Jul 2009 15:42:34 +0200 [thread overview]
Message-ID: <20090729134234.GY13236@buzzloop.caiaq.de> (raw)
In-Reply-To: <F81DF98CADE6064F81A746D7C8323593782CAC@fr-ex009.groupinfra.com>
(please keep the mailing list copied - I'm not your personal supporter,
and others might be interested in that, too.)
On Wed, Jul 29, 2009 at 03:32:52PM +0200, Courousse, Damien wrote:
> > 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?
> [Damien Courouss?]
>
> target/linux/Makefile.in.advanced contains the following:
> $(LINUX26_DIR)/.configured: $(LINUX26_DIR)/.config
> $(SED) '/CONFIG_AEABI=y/d' $(LINUX26_DIR)/.config
> ifeq ($(BR2_ARM_EABI),y)
> echo "CONFIG_AEABI=y" >> $(LINUX26_DIR)/.config
> $(SED) '/CONFIG_OABI_COMPAT/d' $(LINUX26_DIR)/.config
> echo "# CONFIG_OABI_COMPAT is not set" >> $(LINUX26_DIR)/.config
> else
Could you check that this condition is met by adding an echo debug in
there?
> ... and my configuration files look fine to me:
> $ make saveconfig
> (...)
> $ cd local/logica_demo/
> $ grep ABI *
> linux-2.6.28.config:CONFIG_SLABINFO=y
> linux-2.6.28.config:# CONFIG_AEABI is not set
> linux-2.6.28.config:# CONFIG_SECURITY_FILE_CAPABILITIES is not set
> logica_demo.config:BR2_ARM_OABI=y
> logica_demo.config:# BR2_ARM_EABI is not set
> logica_demo.config:BR2_GCC_TARGET_ABI="apcs-gnu"
> uclibc-0.9.30.1.config:CONFIG_ARM_OABI=y
> uclibc-0.9.30.1.config:# CONFIG_ARM_EABI is not set
And what does your $(LINUX26_DIR)/.config look like afterwards? Is EABI
set in there? If so, we'll need to find out why. Could be that there
have been changes in the Linux kernel config which cause EABI to be set,
depending on other config flags, but I don't have a solution at hand
currently. Shouldn't be too hard to figure out, though.
Daniel
next prev parent reply other threads:[~2009-07-29 13:42 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
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 [this message]
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=20090729134234.GY13236@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