Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Still can't build working rootfs with crosstool-NG toolchain
Date: Mon, 19 Apr 2010 18:08:20 +0000 (UTC)	[thread overview]
Message-ID: <hqi66j$i2c$1@dough.gmane.org> (raw)
In-Reply-To: 20100419180637.241cbdd0@surf

On 2010-04-19, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Mon, 19 Apr 2010 14:44:30 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> I've spend the past week trying to use crosstool-NG instead of
>> buildroot to build a toolchain.  I had been using external buildroot
>> toolchains for the past couple months with no problems. But, that is
>> unsupported by buildroot, and I'm giving up fighting that battle.
>
> Come on, it is *not* unsupported. We are trying to support it, but
> facing issues.

I just meant that it doesn't currently work unless I maintain forked
versions of several .mk files (including ext-tool.mk).  I don't want
to do that anymore, so I'm trying to switch to ctNG and abandon my
forked files.

>> It doesn't seem to matter which toolchain I use to build the kernel, I
>> get the same results with both kernels. I'm using an Atmel
>> AT91SAM9G20EK development board, gcc 4.4.3, uClibc 0.9.30.2.
>
> The problem might be related to OABI vs. EABI. What's the
> configuration of the toolchain, the Buildroot configuration, and the
> kernel configuration for this ?

Doh.

It was indeed an OABI vs. EABI problem.  The problem was a result of
daisy-chaining several bits of my own stupidity together:

 1) At one point I had switched the buildroot toolchain to EABI, but
    somehow I switched it back either without knowing or without
    remembering.

 2) I had thought that using an EABI toolchain produced an EABI
    kernel, but it doesn't: there's a kernel configuration variable
    you have to set.  This resulted in my mistaken belief that my
    kernel was EABI and my misinterpreting some testing that I did in
    an attempt to confirm that both toolchains were EABI.

 3) I had a downloaded an EABI kernel uImage file to use for testing
    and didn't realize it had backwards OABI compatibility enabled --
    causing me to stumble even further down the path of believing all
    my different kernels, root filesystems, and toolchains were EABI.

It's all painfully obvious now...
    
-- 
Grant Edwards               grant.b.edwards        Yow! ... My pants just went
                                  at               on a wild rampage through a
                              gmail.com            Long Island Bowling Alley!!

  reply	other threads:[~2010-04-19 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 14:44 [Buildroot] Still can't build working rootfs with crosstool-NG toolchain Grant Edwards
2010-04-19 16:06 ` Thomas Petazzoni
2010-04-19 18:08   ` Grant Edwards [this message]
2010-04-19 17:50 ` Peter Korsgaard
2010-04-19 18:13   ` Grant Edwards
2010-04-20 18:26 ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Microbit_P43000
2010-04-20 23:43   ` Ben Kloosterman
2010-04-21  8:15     ` Microbit_P43000
2010-04-21 14:06       ` Grant Edwards
2010-04-21 16:07         ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 16:31           ` Grant Edwards
2010-04-21 18:25             ` [Buildroot] Still can't build workingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:33               ` Grant Edwards
2010-04-21 18:46                 ` Peter Korsgaard
2010-04-21 22:06                 ` [Buildroot] Still can't buildworkingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:43             ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Peter Korsgaard
2010-04-29 10:03             ` Thomas Petazzoni
2010-04-29 10:07         ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Thomas Petazzoni

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='hqi66j$i2c$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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