Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Linaro Toolchain for RPI and OABI Issues
Date: Tue, 12 Nov 2019 20:15:51 +0100	[thread overview]
Message-ID: <20191112201551.1f1f6190@gmx.net> (raw)
In-Reply-To: <1573542699220-0.post@n4.nabble.com>

Hello rscr,

On Tue, 12 Nov 2019 01:11:39 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hello,
>
> I am new on Buildroot and I am trying to build linux with buildroot for rpi
> zero w.
>
> I have successfully build a first version using the buildroot toolchain but
> now I would like to use the rpi's one.
> (https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64)
>
> My host is running Ubuntu 16.04 on a 64-btis system.
>
> The problem is that when building I get :
>
> "External toolchain uses the unsuported OABI"
>
> I am confused. I thought the rpi's toolchain is using the eabihf, is not?
>
> Find attached my _defconfig.
>
> Thanks in advance,
>
> Rafa cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>

Could not reproduce your build problem using your given defconfig, did a fresh checkout of

	$ cd my_toolchain_patch
	$ git clone https://github.com/raspberrypi/tools.git

And adjusted

BR2_TOOLCHAIN_EXTERNAL_PATH="<my_toolchain_path>/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64"

Builds fine here (openSUSE Tumbleweed)

Regards,
Peter

>
>
>
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-11-12 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12  7:11 [Buildroot] Linaro Toolchain for RPI and OABI Issues rscr
2019-11-12 19:15 ` Peter Seiderer [this message]
2019-11-13 13:07   ` rscr
2019-11-13 21:13     ` Peter Seiderer
2019-11-14 13:53       ` rscr
2019-11-14 14:15         ` Peter Seiderer
2019-11-15  7:27           ` rscr

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=20191112201551.1f1f6190@gmx.net \
    --to=ps.report@gmx.net \
    --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